Hi All,
For cross-team planning purposes, it makes sense for us to have our two-week development cycles aligned with those of the rest of the Firefox org. The broader org are scheduling work based on three two-week development iterations in each six-week Firefox release cycle. They're starting "iteration 42.3" this week, the third and final two-week iteration while Firefox 42 is on Nightly. We're halfway through our train-43 development cycle, meaning we're misaligned by a week. I propose that once train-43 is out the door, we do a three-week train to get into alignment: * Week of 3rd August: train-43 tagged, train-44 begins * Week of 10th August: train-43 deployed, Firefox 40 released * Week of 24th August: train-44 tagged This would put us squarely in alignment with the Firefox 43.X development cycles, like so: * Firefox 43.1 == FxA train-44 * Firefox 43.2 == FxA train-45 * Firefox 43.3 == FxA train-46 * etc... At which point we might consider just adopting their naming scheme as well, but let's not change too many things at once :-) It would also mean that we have our train *deployments* offset by a week from Firefox releases, unlike train-43 with is scheduled to go live the same week as the Firefox 40 release. I think this will be a good thing for overall release and quality management. Thoughts? Ryan _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
