On 1/13/2015 11:07 AM, Bhavana Bajaj wrote:
Hi all, We've recently completed all the mergeday related mechanics for FxOS 2.2 which includes creating gaia v2.2 <https://github.com/mozilla-b2g/gaia/tree/v2.2>/mozilla-b2g37_v2_2 <http://hg.mozilla.org/releases/mozilla-b2g37_v2_2/> branches as of 1/12. The current central/master is dedicated to our next release (v3.0). Also following are the cset on 2.2 right before we merged. * Last Gaia on v2.2 is https://github.com/mozilla-b2g/gaia/commit/b0254d13e67b0bd4c74c2f2c9b9ea1251949d9fe * Last Gecko revision merged is http://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2c951493eef5 *2.2 Status :* https://wiki.mozilla.org/FirefoxOS/TwoDotTwoTracking/Dashboard is being used to track the must have feature list for 2.2 and gives you a picture of all the Resolved bugs and outstanding work. We will continue to uplift the remaining work to ship this release. <https://wiki.mozilla.org/FirefoxOS/TwoDotTwoTracking/Dashboard> *Landing/Approval policies :* * Any landings henceforth on the 2.2 branch specifically, needs to go through approval process (including blocking-b2g:2.2+ bugs). Please set approval-gaia-v2.2 or approval‑mozilla‑b2g37? on the patch attachment for us to consider these uplifts. Once the patch is approved automatic uplifts will continue to happen on these by the sheriff's as usual (Ryanvm and his team , Thanks!) ** What can land ?* ** Any remaining feature-b2g:2.2+ or blocking-b2g:2.2+ bugs can continue to land. EPM's/RM/Engg managers are scrubbing the list to make sure these feature blockers are indeed needed in 2.2 ** We will consider uplifting any polish/performance/stability bugs (although non-blocking) until the 2.2 feature landing milestone on February 23, if that helps us improve the quality. Please note we will evaluate the risk/reward when considering these approvals and no guarantee's that *all* the patches will be approved. ** Gecko Landings:* ** Please note that b2g has diverged from mainline gecko and is on its own b2g37 branch. mozilla-aurora <https://hg.mozilla.org/releases/mozilla-aurora> (gecko 37) will continuously be merged to mozilla-b2g37_v2_2 <http://hg.mozilla.org/releases/mozilla-b2g37_v2_2/>. So, if you have a gecko bug that you are fixing on aurora and impacts b2g as well, you do not have to worry about requesting approval twice as the sheriff's will auto-merge it for you. *Helpful wiki's:* * Branch/Landing information : https://wiki.mozilla.org/Release_Management/B2G_Landing#v2.2 * Approvals/Uplifts : https://wiki.mozilla.org/Release_Management/Uplift_rules * FxOS v2.2 Schedule : https://wiki.mozilla.org/Release_Management/FirefoxOS/2_2_Schedule#Detailed_Sprint_schedule Feel free to ping/email me directly, if you have a question/concern or need more information. Thanks, Bhavana Bajaj irc: :bajaj -- --Bhavana Bajaj
Since we've had multiple instances of this happening lately, a friendly reminder that having blocking-b2g:2.2+ or feature-b2g:2.2+ status does *NOT* grant auto-approval for uplift. You still need to go through the regular approval process. The reason for this is that while blocking/feature status says "we want this fixed for 2.2", approval says more specifically "this patch is an acceptable way to fix the problem for 2.2".
Thanks, Ryan _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
