Hi! Thanks for clarifying.

Regards

Marce

El 19/09/2013, a las 21:04, Alex Keybl escribió:

> Our very own jhford and ryanvm will continue to perform uplifts once 
> Resolved/Fixed, as long as there are no conflicts. Those patches with 
> conflicts will have the branchpatch-needed keyword added, and will require 
> followup from a developer.
>
> Keep in mind that this means all patches landed on a koi+ bug will be 
> uplifted automatically to 1.2, unless otherwise specified. Be mindful of 
> landing unnecessary strings or other changes in 1.2 :)
>
> -Alex
>
> On Sep 19, 2013, at 2:51 PM, MARCELINO VEIGA TUIMIL <[email protected]> wrote:
>
>> Hi! About landing and uplifting, who has to do it? Until now developers land 
>> in master, and release engineers uplift to the final branch. Is it the same 
>> way?
>>
>> Regards
>>
>> Marce
>>
>> El 18/09/2013, a las 22:22, Alex Keybl escribió:
>>
>>> Most of the notes below pertain to 1.2, but 1.3 feature development and 1.4 
>>> planning will of course begin ramping up soon.
>>>
>>> -Alex
>>>
>>> =This week=
>>> * mozilla-central/master are now v1.3, and 1.2 is now branched
>>> * We are reviewing any misses for 1.2 committed features, and finding out a 
>>> risk evaluation and ETA
>>> * Mozilla QA is shaking down 1.2 to find as many regressions as possible - 
>>> currently 60% of the way through test cases
>>> * Release Management prioritizing triage/investigation of critical issues 
>>> in new features and performance regressions
>>> * Release Management is finding/fixing holes and slow points in per-team 
>>> blocker triage
>>>
>>> =Until October 28=
>>> * Gecko 26 (the underlying 1.2 platform version) will be on mozilla-aurora
>>> * Gaia 1.2 has moved to the 1.2 branch
>>> * A bug will only land in v1.2 if it is marked with blocking-b2g:koi+ or 
>>> the patch has gotten an exception through either approval-mozilla-aurora+ 
>>> or (Gecko) approval-gaia-v1.2+ (Gaia)
>>> * Individual functional teams are responsible for triaging incoming blocker 
>>> nominations
>>> * String/l10n changes will only rarely be granted
>>>
>>> =After October 28=
>>> * Release Management will take over triage of blockers, and exceptions will 
>>> no longer be granted
>>> * A bug will only land to v1.2 with blocking-b2g:koi+
>>> * OEM testing cycles should begin no later than October, if fixes are 
>>> desired for newly found issues
>>> * String/l10n changes will almost never be granted
>>> * B2G 1.2's Gecko will branch from Firefox for Desktop/Mobile
>>>
>>> =After December 9=
>>> * Mozilla will move focus away from 1.2 outside of security fixes
>>>
>>> =Resources=
>>> * 1.2 Functional Team Reviews (team queries are still being tweaked): 
>>> https://wiki.mozilla.org/FirefoxOS/OneDotTwoTracking
>>> * Branch/Landing information, just updated: 
>>> https://wiki.mozilla.org/Release_Management/B2G_Landing
>>> * B2G 1.2 triage info, to be updated with 1.3 blocking info shortly: 
>>> https://wiki.mozilla.org/B2G/Triage
>>> * 1.3 Functional Team Reviews: incoming
>>> * [email protected], if you have a question or a bug you've 
>>> nominated isn't getting the attention it deserves
>>> _______________________________________________
>>> dev-b2g mailing list
>>> [email protected]
>>> https://lists.mozilla.org/listinfo/dev-b2g
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
>> nuestra política de envío y recepción de correo electrónico en el enlace 
>> situado más abajo.
>> This message is intended exclusively for its addressee. We only send and 
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra política de envío y recepción de correo electrónico en el enlace 
situado más abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to