[just dev-b2g] If it wasn't already clear from https://etherpad.mozilla.org/b2g-convergence-landing, we need to maintain all of the same platform changes on all branches from FF18 and up (mozilla-central, mozilla-aurora, mozilla-beta). There are a number of reasons why we are maintaining this process. To name a couple:
* we want web app developers to be able to target all versions of Firefox, 18 and up, in the same way * hunting down amorphous platform regressions that are inconsistent across versions is a hellish feat * maintaining repositories (security fixes, stability fixes, etc.) when code changes are unnecessarily inconsistent from one to the next is just plain silly This has always been the plan, and will continue to be. Thanks for reading. -Alex On Nov 19, 2012, at 6:28 PM, Alex Keybl <[email protected]> wrote: > [x-post to dev-b2g and dev-gaia] > > We're now in the C2 milestone until 12/10, and plan to make sure that all > bugs meeting the C2 criteria are properly milestoned tomorrow. See > https://etherpad.mozilla.org/b2g-convergence-schedule for more info on the C2 > criteria. > > We've also updated https://etherpad.mozilla.org/b2g-convergence-landing to > extend the C1 landing process into at least the first week of C2. Moving to > approvals-only later in C2 is meant to help drivers vet the testing performed > on patches before landing, to prevent new major regressions that hurt ongoing > QA/dogfooding testing. > > The more testing you all do, the less regressions we have, and the longer > we'll be able to extend the current landing process. > > -Alex > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
