The Gecko and gaia have interdepedencies and the plan was to release 44 with gaia 2.5. Because of the depedency, when gecko branched, we also branched 2.5.
On Wed, Nov 4, 2015 at 9:48 AM, Francesco Lodolo [:flod] <[email protected]> wrote: > Hi Naoki, > The reason why we branched early was clear (on Gecko's side), what I > couldn't understand was the plan for Gaia's branch. > > I still find the communication around this process partial and confusing – > maybe that's just me, being involved only partially in Gaia – but at least > now the branch has been updated as I expected (i.e. not cherry-picking > single commits) > https://github.com/mozilla-b2g/gaia/commits/v2.5 > > Francesco > > Francesco, the answer to your question on why 2.5 got branched earlier : > > https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/e71M1z0YE_g > > Platform made their own decision without seeing where they would break. > We were forced into moving to 2.6 because of the 44 to 45 branch and we're > locking 2.5 to 44. > > We (QA) were just as confused when we found this out on friday. > Effectively they terminated our 2.5 project foxfooding early as we have no > Aries 2.6 and 2.5 builds on taskcluster even as of today. We're back on > testing on flame as buildbot is still pumping out the 2.5 / 2.6 builds in > the interim. > > > On Tue, Nov 3, 2015 at 11:56 PM, Francesco Lodolo [:flod] < > <[email protected]>[email protected]> wrote: > >> If that's the case I find it extremely confusing: branch date for Gaia >> was supposed to be November 2nd, the current tip on v2.5 is from 6 days ago. >> >> I've seen probably a dozen changesets with strings landing during the >> last week-end before the planned merge day, I suppose the ones with just >> code are a lot more (was this change communicated to devs?). >> It would seem more reasonable to define a "tip" changeset on master and >> pull all the previous commits into v2.5, then deal with back-outs on the >> branch and eventual uplifts from master. >> >> Francesco >> >> Hi Francesco, >> >> I think the uplift approval process is for both Gecko ( >> *approval‑mozilla‑b2g44?*) and Gaia (*approval-gaia-v2.5?*) >> >> Cheers, >> Josh >> Engineering Program Manager, Firefox OS >> >> On Nov 4, 2015, at 3:23 PM, Francesco Lodolo [:flod] <[email protected]> >> wrote: >> >> Hi, >> I've asked this before but didn't get a clear answer: are we talking >> about uplifts for Gecko or Gaia (master to v2.5 branch)? >> >> Francesco >> >> Hello, >> >> As Gecko 44 branched out earlier (10/28) than planned (Nov 2nd), we will >> uplift all 2.5 patches landed on Master to 2.5 branch. Sheriffs are >> uplifting patches that landed later than 10/28. >> >> For any patches that are not 2.5+ to land on 2.5, they will go through >> the regular uplift approval process. Please set the flags >> *approval-gaia-v2.5?* and >> >> *approval‑mozilla‑b2g44? * >> Thanks for the great work on 2.5 so far. Lets continue the good work to >> land the 40 blockers yet to fix. >> >> For any questions or concerns please email/buzz me. >> >> Thank you, >> >> Mahe >> >> -- >> Mahendra Potharaju >> >> >> _______________________________________________ >> dev-fxos mailing >> [email protected]https://lists.mozilla.org/listinfo/dev-fxos >> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> >> >> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> >> > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
