QA/Desktop Firefox/Walkthroughs/Iteration Development: Difference between revisions

Some bugs will inevitably land too close to migration for QA to qualify in time. We will allow these bugs to ride the train to Aurora but they will carry over to the next iteration as a work item. If we find issues during that first Aurora iteration we will request a backout. That said, we would encourage only low-risk changes land in the last few days of the last iteration; high risk changes should wait for the next iteration to land. This is not just to ensure regressions don't sneak in but also reduces the likelihood of a risky/messy backout. As we get closer to migration landing approvals should be looked at through the lense of Aurora uplift. In other words, would Release Management approve your request for uplift if your patch was coming after migration? If the answer is ''no'' then we'd be inclined to ask you to hold off on landing the patch until after migration.