This is important! Please read! RyanVM and jhford are going to start uplifting tracking-b2g18+ bugs automatically up until feature complete (3/15), assuming that any tracked/resolved bugs that do not have NO_UPLIFT in the whiteboard meet this criteria:
> 2) The bug has already landed to mozilla-central/master > 3) The bug is considered low risk > 4) The bug has no l10n impact 5) The bug remains fixed on m-c/master after two days ** If a tracked bug you're working on does not meet these requirements, please add NO_UPLIFT to the whiteboard and request approval when desired.** In the future, to see if a bug will be automatically uplifted, please check the lists at https://wiki.mozilla.org/Release_Management/B2G_Landing#Automatic_Uplifts. -Alex On Mar 1, 2013, at 5:46 PM, Alex Keybl <[email protected]> wrote: > Hi all, > > We've just updated https://wiki.mozilla.org/Release_Management/B2G_Landing to > reflect the fact that we're opening up landings to mozilla-b2g18/v1-train > without approval until 3/15, if: > > 1) The bug has tracking-b2g18+ > 2) The bug has already landed to mozilla-central/master > 3) The bug is considered low risk > 4) The bug has no l10n impact > > All other non-leo+ changes should continue to go through the approval-gaia-v1 > and approval-mozilla-b2g18 process. Similarly, after 3/15, all non-leo+ > changes must go through approvals. > > We've also added a new "Versions and Scheduling" section to the wiki that > should clear up some of the associations between versions, dates, codenames, > security fixes, etc. > > -Alex > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
