-
Notifications
You must be signed in to change notification settings - Fork 859
RMManagementOfBugs
Jeff Squyres edited this page Sep 10, 2014
·
6 revisions
The following is a rough outline of how bugs are managed in a given release series:
- Working assumptions
- Bugs with labels of "blocker" or "critical" are needed to be fixed for the official release.
- Bugs with a "minor" label (or no severity label) and below may be fixed but will not be driven to be fixed by the RMs.
In order to make sure the bugs that progress is being made on the appropriate bugs the RMs will review the bugs weekly and do the following:
- Assign owners to unowned bugs of priority "blocker" or "critical"
- Request owners to update bugs that have not been updated in 2 weeks.
- Technical Background
- Projected timeline as to when a fix might be available.
- Engage owners of bugs in a discussion as to whether certain bugs are prioritized correctly.
- Review requests to reprioritize bugs.
Near the time a release is to be officially released, the RMs will review the current set of blocker and critical bugs to determine if any should be postponed.