In the current model, each release is in development for a total of 24 weeks (12 for feature development, 12 for convergence). It's then supported with security patches for another ~6 months. Sorry, I don't understand your question perfectly so I'm just trying to provide context.
> If you want to reduce maintenance cost, change the desktop ESR versions to > repeat after an _even_ number of desktop cycles so desktop ESRs always use > the same Gecko branch like a FxOS release branch. At the moment, every 7th > Gecko branch is an ESR. This is something we'll definitely want to take into consideration in the future, thanks for the suggestion! As of right now, there's 6 weeks during convergence where we may have minor divergence from desktop Firefox since we may take some risk for B2G that we don't need elsewhere. -Alex On Jul 21, 2013, at 3:29 PM, Archaeopteryx <[email protected]> wrote: > Hi, > > congratulations to pushing FxOS to the public. > >> Now that we have our v1.0 behind us and we’re moving forward with >> even more partners, we’re going to do our best to bring Firefox OS >> back into our heartbeat and will make quarterly feature releases >> available to partners along with six-weekly security updates for the >> previous two feature releases. As far as I know, that’s the most >> aggressive mobile OS release strategy out there (and may still >> require some tweaking). > So you provide 9 months in which partners can test builds which they > want to push to the customers? If the builds, APIs etc. in the first > three month when the customers are up to date won't be unstable. If you want > to reduce maintenance cost, change the desktop ESR versions to repeat after > an _even_ number of desktop cycles so desktop ESRs always use the same Gecko > branch like a FxOS release branch. At the moment, every 7th Gecko branch is > an ESR. > > Archaeopteryx > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
