On Wed, Apr 3, 2013 at 8:16 PM, Jonas Sicking <[email protected]> wrote:
> This actually means that we would have the ability to go back to > mozilla-central and gaia master right now and ride the normal release > trains for the Gecko 23 release, while still reaching the release > milestone for gecko before v1.1 is done. > I won't try to speak for the gecko part, because I understand there are challenges in syncing Firefox release schedules with Firefox OS release schedules. But from Gaia's point of view I absolutely support going back to using master for 1.1. I'd like to see us branch gaia releases as late as possible (if at all), and only allow bugfixes on that branch (not new features or enhancements). Right now a very large proportion of patches on master are getting uplifted to v1-train anyway, and many of those that aren't uplifted end up being uplifted later because there turn out to be unexpected regressions due to dependencies and bad merges. Once we switch to two week iterations of development post-1.1 presumably those iterations will happen in master too? Ben _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
