> So for me it's clear than approval-gaia-v1 and approval-mozilla-b2g18 can > follow the shira+ rules above and land to v1.0.1 branches/repos, at least, > until the end of this week.
We will be approving some non-tef+/shira+ (for instance UX critical bugs) for landing on the v1.0.1 branches, and we'll be very explicit in our comments when we do so. -Alex On Feb 14, 2013, at 1:50 AM, Mª ANGELES OTEO MARTINEZ <[email protected]> wrote: > Hi, > According to the wiki > (https://wiki.mozilla.org/Release_Management/B2G_Landing#TL.3BDR) > > > Landing tracking-b2g18+ bugs for v1.x > * r+ is required > * Land to master (Gaia) <https://github.com/mozilla-b2g/gaia> or > mozilla-central (Gecko) <https://hg.mozilla.org/mozilla-central/> and mark > the bug as Resolved/Fixed > * If things look good on master / mozilla-central, then nominate for > approval-gaia-v1 or approval-mozilla-b2g18. Once approved, upliftto: > > * v1-train/mozilla-b2g18 (setting status-b2g18:fixed) > > * v1.0.1/mozilla-b2g18_v1_0_1(setting status-b2g18-v1.0.1:fixed) > > * Until 2/18, approval-gaia-v1 and approval-mozilla-b2g18 can follow the > shira+ rules above and land to v1.0.1 branches/repos > > > > > So for me it's clear than approval-gaia-v1 and approval-mozilla-b2g18 can > follow the shira+ rules above and land to v1.0.1 branches/repos, at least, > until the end of this week. > Correct me, Alex, if I am wrong. > > Regards > Maria > > > El 14/02/13 09:54, "MARCELINO VEIGA TUIMIL" <[email protected]> escribió: > >> Hi! My understanding until now was that branch v1.0.1 would be created on >> 2/13, but the official branching date would be 2/15, so until then all a+ >> bugs would be uplift to v1.0.1 branch also. Please, can you clarify? >> >> Regards >> >> Marce >> >> El 14/02/2013, a las 03:36, Justin Lebar escribió: >> >>> If you're using hg, here are instructions for cloning b2g18-v1_0_1 >>> quickly, given another existing Gecko clone: >>> >>> http://jlebar.com/2011/5/20/Faster_and_smaller_clones_of_branches.html >>> >>> In other news, I think Ehsan is on vacation this week, so >>> http://github.com/mozilla/mozilla-central does not have the >>> b2g18_v1_0_1 branch. >>> >>> But John Schoenick has graciously added a b2g18_v1_0_1 branch to his >>> Gecko repository on github. His repository has the same hashes as >>> Ehsan's, so you should be able to develop using his remote and then >>> seamlessly switch back to Ehsan's once his repository adds this >>> branch. >>> >>> The procedure is >>> >>> $ git remote add johns git://github.com/Nephyrin/mozilla-git.git >>> $ git fetch johns >>> $ git checkout johns/releases/b2g18_v1_0_1 >>> >>> Thanks, John! >>> >>> Happy hacking, >>> -Justin >>> >>> On Wed, Feb 13, 2013 at 5:46 PM, Alex Keybl <[email protected]> wrote: >>>> RelEng has just completed the v1.0.1 branching (thanks rail, joduinn >>>> and all) in preparation for this weekend's code handoff. >>>> >>>> What does that mean for you? If you land your own changes, check out >>>> [1]. If you're still working on tef+, shira+ (due 2/15!), or UX >>>> critical bugs, please continue to burn them down as your highest >>>> priority. If you have any resolved leo+ bugs, it's now OK to start >>>> uplifting your work to mozilla-b2g18/v1-train. >>>> >>>> A quick post-branch overview of what to land where follows. >>>> >>>> v1.0.0: mozilla-b2g18_v1_0_0/v1.0.0 >>>> - No longer needs to be maintained, remaining tef+ bugs land to v1.0.1 >>>> v1.0.1: mozilla-b2g18_v1_0_1/v1.0.1 >>>> - Only tef+ and shira+ bugs are landing to these branches >>>> - Over the next few days, some non-blocking approvals (UX critical >>>> bugs) will also be uplifted to v1.0.1 >>>> v1.1: mozilla-b2g18/v1-train >>>> - All tef+, shira+, and leo+ bugs as well as approvals are landing to >>>> these branches >>>> v2: mozilla-central/master >>>> - Anything with an r+ goes >>>> >>>> If you've any questions about what to land where, please read [1] and >>>> feel free to contact myself, lsblakk, or anyone in RelEng ([email protected]). >>>> >>>> -Alex >>>> >>>> [1] https://wiki.mozilla.org/Release_Management/B2G_Landing#TL.3BDR >>>> >>>> On Feb 8, 2013, at 12:14 AM, John O'Duinn <[email protected]> wrote: >>>> >>>>> hi; >>>>> >>>>> In preparation for the v1.0.1 drop on Friday 15feb, we're turning the >>>>> v1.0.1 branch mechanics live early on Wednesday 13feb. This means that >>>>> if you are landing any v1.0.1 changes *after* the branch point on >>>>> Wednesday 13th, you will need to also land your changes on: >>>>> gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/ >>>>> gaia: https://github.com/mozilla-b2g/gaia/tree/v1.0.1 >>>>> >>>>> I will send followup post here when the branching is actually live. >>>>> >>>>> Note: >>>>> *) No change to the handover-to-partner deadline of 15feb. >>>>> *) No change to the bugzilla tags being used to track fixes and >>>>> approvals-for-landings. >>>>> >>>>> This proposal is already approved by agal, akeybl, dietrich and >>>>> partners, but if there is a reason this should not happen, or there is >>>>> something we missed, please let me know. >>>>> >>>>> John. >>>>> ===== >>>>> ps: Further background for the curious: >>>>> >>>>> 1) This allows us to verify builds+updates are successfully generated >>>>> and tested on the v1.0.1 branch in advance of the 15th deadline. >>>>> 2) This allows us to have downstream partners switch to the new >>>>> v1.0.1 branch on (or maybe even before) the 15th. >>>>> 3) This keeps b2g branch mechanics on separate date from the FF19 >>>>> migrations and builds, which happen on the 15th. While different >>>>> personnel are involved, the FF19 and b2gv1.0.1 branching mechanics >>>>> each >>>>> have a lot of moving parts, so this feels prudent. >>>>> 4) This means that any late-breaking 1.0.1-specific-fixes would need >>>>> to >>>>> do one additional landing on the v1.0.1 branch. >>>>> >>>>> ===== >>>>> _______________________________________________ >>>>> 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 >>> _______________________________________________ >>> 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 >> _______________________________________________ >> dev-gaia mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-gaia > > > ________________________________ > > 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
