That's a good idea. Should we file a bug to do this? Sincerely, Jason Smith
Desktop QA Engineer Mozilla Corporation https://quality.mozilla.com On 4/10/2013 5:14 PM, Gregory Szorc wrote:
On 4/10/2013 1:38 PM, Jason Smith wrote:Hi Everyone, Right now, when a landing occurs, my understanding is that we're typically setting the target milestone field to what Firefox release the code lands on if it lands on trunk. If a patch is uplifted, then the status flag is set appropriately for the target Firefox release. However, after working with three distinct teams, talking with Ed, and analyzing status flag usage, I have seen these contention points dependent on a team's method for tracking that might happen: * The need for a particular team to track the concept of "We would like to get this fixed in this Firefox release." Some teams I've worked with have considered using the target milestone field here, but that collides with the trunk management definition, which often causes contention during the landing or post landing process. * The need to be able to query the status-firefox flags to determine when a patch lands on a per branch basis even if has landed on trunk. This helps for those tracking fixes to use one universal flag to query on to determine such things such as: o What bugs that are features are worth verifying on X branch? o What bugs that defects are worth verifying on X branch? Knowing this, why not consider just using the status-flags purely to track landings and let the team determine how to use target milestone? Also, why not set the status-flag in general for the appropriate Firefox release when a patch lands on trunk?I don't really have much to say on the specifics of this post other than a simple question: why don't we have a checkin hook or bot automatically update Bugzilla flags when changesets are pushed? This would save developer time and would reduce the error rate of bugs not updated properly (especially when you consider that policies change over time).
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
