Now that we have three versions in flight at any one time — 2.1 in release, 3.0 in stabilization, 4.0 in master — we need to be a little more disciplined in our use of flags. Regression hunting and answering release-related questions means knowing which releases are affected by bugs, and also when and where fixes and features landed.
Here's my proposal, as discussed today. It's based on what we do for Android. - When a bug is found in a release, set *status-fxios-vM.N* to *affected*. If a release isn't affected, mark it as *unaffected*. - When a commit lands in master, set *Target Milestone* to the current trunk version. Right now that's 4.0. - When you do so, mark the bug as RESOLVED FIXED and include a link to the commit in a comment. - If this bug doesn't affect the release in stabilization, you're done. Otherwise, after preconditions are met — the change didn't bounce for breaking tests, and someone verified that it fixed the bug — request uplift via *[needsuplift]*. We'll walk through this list twice per week, making a decision about risk/reward. After approval: - Land the fix in the *vM.0* branch. - Paste a link to the commit in a comment. - Set *status-fxios-vM.0* to fixed. - Set other versions' status flags to *wontfix* if applicable. A bug that was first fixed today, then uplifted to v3.x, but also affected 2.1, will have: status-fxios-v2.0 = wontfix status-fxios-v3.0 = fixed (and later *verified*) Target Milestone = 4.0 Status = RESOLVED FIXED This combination lets us answer questions like: - What fixes went into 3.0? Target=3.0 *or* status-fxios-v3.0=fixed - Which bugs have a fix that wasn't uplifted to 3.0 yet? status-fxios-v3.0=affected *and* status=FIXED - Which fixes were uplifted (and thus might have fixed or introduced a regression)? Target > 3.0 *and* status-fxios-v3.0=fixed - Etc. Comments or questions welcome. I'll dump this on the wiki/GitHub a little later.
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
