Auto-tools/Projects/Proposed/ChangeBugsOnLandBackout
From MozillaWiki
< Auto-tools | Projects | Proposed
Feature | Status | ETA | Owner |
Bug Flag Mgmt on Land and Backout | Proposed | 2011-05-10 | TBD |
Summary and Goal
When you back something out from aurora or the proposed mozilla-random, or m-c, there is a set of bugzilla flags that will need to be reset, comments need to be made, etc. If we move toward a more automatic landing system, we need something to help manage these flags. This is a first stab at such an automation, for use by sheriffs or developers who need to back a set of changes out of one of the trees and reset the bugzilla flags appropriately
Proposed By
Sdwilsh, Ehsan
Ideal ETA
??
Requirements/Features
If you want to leave some ideas on requirements/features/thoughts, do so in a section under your name. That makes it easy to come back to you if we have questions later.
We'll file bugs once we have nailed down what we're implementing.
Ctalbert
- It should have a finite set of fields for changing upon backout, perhaps presented as name/value pairs.
- Each field should specify an "original" state that it expects to find the field in and a "final" state that it expects to set the field to.
- It should pull as much data from the commit message of the changeset as possible.
- If the change is already made or the flag it intends to set is not in the expected "original" state, the tool should not attempt to change it. (It assumes a human has already made the change)
Use Cases
- What flags should this be setting?
- Could this be useful for both people performing backouts as well as people merging data into mozilla-central/aurora/beta?
Related Bugs, Dependencies, & Starting Points
Non-Goals
- Not replacing bugzilla UI, just streamlining the case where you have to change several flags on many bugs at once because of an action in our source repo (i.e. an action in hg causes changes in bugzilla).
- It's not going to be worth the time for single changes, only for very complicated changes requiring several fields on several bugs.
- Not going to be a general purpose bugzilla-bug-modifier. It should only solve this niche problem until we tie the source repo more closely with bugzilla.
Other Stuff
Legend (remove if you like)
Healthy: feature is progressing as expected. | |
Blocked: feature is currently blocked. | |
At Risk: feature is at risk of missing its targeted release. | |
ETA | Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date. |