On Wed, Apr 3, 2013 at 4:32 PM, Andreas Gal <[email protected]> wrote: >> >> 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'm not sure I completely understand this proposal. But if you're suggesting that we do everything the same except we avoid checking in patches for 1.2 into trunk, I don't think that improves the situation much. In my experience, little 1.2 work is ongoing compared to the amount of regular Gecko work that gets checked in every cycle. As a result, it's not the B2G 1.2 work that's causing the painful divergences between m-c and the 1.1 branch for me. It's good to give people an outlet for 1.2 work that they're doing, otherwise they'll argue harder to get it into 1.1, which is unhelpful. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
