That works for some features and code changes but not all. v1.1 stabilization has started _NOW_. Going forward every time we touch the code we risk breaking something, even when landing code thats disabled by default. So until yesterday it would have been ok to land v1.2 work on v1.1 as long its disabled. From now until we ship v1.1 its not really a viable option due to stability concerns.
Andreas On Apr 4, 2013, at 11:28 AM, Julien Wajsberg <[email protected]> wrote: > Le 03/04/2013 22:32, Andreas Gal a écrit : >>> I don't think keeping v1.1 and trunk close is a goal of release >>> drivers. Their goal is to stabilize 1.1 by denying approval for risky >>> patches. That is directly at odds with keeping trunk and 1.1 close. >> What about the other option? Avoid v1.2 work until v1.1 is more stable? >> > > I see no particular problem in landing 1.2 work in a 1.1 branch (which > can be master/m-c). We can disable it if it's not stable enough when in > the stabilizing phase (as we do on Firefox AFAIK). > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
