[x-post to dev.gaia and dev.b2g, reply on dev.gaia for this one] In talking with a few devs recently, I've realized that we don't have a universal backout policy for FxOS development and pre-release branches (more true on the Gaia side). My proposal would be that if you run into any of the following issues, somebody (likely you) should immediately identify and backout the regressing bug on affected branches:
* Test failure (intermittent or otherwise) * Unexpected functional regressions, especially those impacting your ability to use the branch as your daily OS * Major/obvious visual issues, especially those preventing demoing of a device * Unexpected performance regressions (in a measured test) Am I missing anything? Do we agree that all devs are responsible for backing out regressing patches according to the above criteria, regardless of what team landed the forward change? Are there any remaining blockers to implementing a backout policy? We have developers and testers working off of these branches around the clock, so we can't afford to have a major regression remain on branches for more than hours. Changes can always re-land once new regressions are ironed out. -Alex _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
