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]
<mailto:[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 list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
_______________________________________________
dev-fxos mailing list
[email protected] <mailto:[email protected]>
https://lists.mozilla.org/listinfo/dev-fxos
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
