Obviously we don't land stuff willy-nilly on master, but at the same time work is incremental, and release branches exist for a reason - our CI is not perfect, and some regressions take some time to show up. In the next few weeks I for one have 3 major-ish changes I want to land (bugs 1161229, 1169012 and 1036697) and I would be pleasantly surprised if I have no follow-ups filed for stuff I missed, or short-term backouts. Maybe I'm just rubbish at this, but that seems par for the course. Anyhow rather than debate the release strategy, consider this a heads-up - I can postpone the FTU refactor, but I think the task manager changes are both timely and important. Let me know if I can do anything to mitigate the risk to stability and the upcoming spark deadline.
On Fri, Jun 5, 2015 at 5:21 PM, Douglas Sherk <[email protected]> wrote: > Hi all, > > Spark is launching soon. It's based on Gaia master and Gecko > mozilla-central, so we'd appreciate it if you avoided landing risky patches > for 3 weeks while we stabilize. Alternatively, you could have your patches > tested very heavily before landing. > > You can see our current timelines here: > > https://wiki.mozilla.org/Release_Management/B2G_Landing#Versions_and_Scheduling > > Thanks for your patience and understanding. > > Doug > > _______________________________________________ > 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
