[b2g] m-c/master is now 2.1, 2.0 has branched

[Bhavana Bajaj]

We've recently completed all the mergeday related mechanics, here's where we are and a few details on how upcoming releases look until next merge.

=This week=

* mozilla-central/master are now v2.1, and 2.0 is now branched

* We will be reviewing any misses for 2.0 features with EPM's, and should have a full list of user stories that made the FL milestone sent-out before end-of-week

** As of now, these are the remaining bugs  http://mzl.la/1p3AS9S still targeted for 2.0 (List is actively being scrubbed)

** Any non-blocking bugs, need to go through approval process. This also applies to any feature work that has been granted exception to land after FL

* String/l10n changes will only rarely be granted until 6/20. Please ensure to add the late-l10n keyword on any string changes beyond today and get them landed before 6/20

** Pending L10n branching for 2.0 : Bug 1022611 - Branch gaia-l10n/* for Firefox OS 2.0, July 21st

* Security uplifts are no longer needed on the B2G18/1.1HD/B2G26 branches as these have EOL'ed

* Product team is working on 2.1 feature planning and https://wiki.mozilla.org/B2G/Roadmap should be updated soon along with more messaging on detailed schedule

* Wrapping up work on 1.4 and stabilization for 1.4

* QA to focus on 2.0 and continue to run full testrun's

* For v2.1 we will only have automation tests and no manual QA effort will be spent on this branch until we wrap up 1.3T work

Note** : Any 2.0 landing that breaks QA smoketests needs to through approval process to get it landed the second time on 2.0 branch. This applies to blocking-b2g:2.0+ bugs as well.

=Until July 21th (next merge)=

* Gecko 32 (the underlying 2.0 platform version) will be on mozilla-aurora

* Gaia 2.0 has moved to the 2.0 branch

* A bug will only land in v2.0 if it is marked with blocking-b2g:2.0+ or the patch has gotten an exception through either approval-mozilla-aurora+ or (Gecko) approval-gaia-v2.0+ (Gaia). Gaia approval requests will not be encouraged after 7/7 and the bar to approve bugs will get higher as we get towards the end of stabilization

=Resources=

* Per team blockers : http://charts.mozilla.org/ffos/blockers.html#responsibility=FxOS_Team&project=1.3,1.3T,1.4,2.0

* Branch/Landing information : https://wiki.mozilla.org/Release_Management/B2G_Landing 

* Uplift Guidelines : https://wiki.mozilla.org/Release_Management/Uplift_rules#General

* https://wiki.mozilla.org/RapidRelease/Calendar

* Triage times and queries :https://wiki.mozilla.org/B2G/Triage#Triage_for_2.0.0

* releas...@mozilla.com, if you have a question or a bug you've nominated isn't getting the attention it deserves

Thanks,

Bhavana Bajaj

irc: :bajaj

[Anthony Ricaud]

On 10/06/14 03:09, Bhavana Bajaj wrote:
> =Until July 21th (next merge)=

> * A bug will only land in v2.0 if it is marked with blocking-b2g:2.0+ or
> the patch has gotten an exception through either
> approval-mozilla-aurora+ or (Gecko) approval-gaia-v2.0+ (Gaia). Gaia
> approval requests will not be encouraged after 7/7 and the bar to
> approve bugs will get higher as we get towards the end of stabilization

I thought there was a period where each functional team was responsible
for managing uplifts at their own discretion. Was I dreaming or is it a
change of policy for this cycle?

Also, do you have a link to a schedule of when those approval requests
are looked at? In the past, I've had to actively reach out to people to
get my approval in a timely manner (aka less than a week). This is
slowing us down because we have duplicate bugs opened waiting for the
uplift to happen.