Thunderbird/Proposal: New Release and Governance Model: Difference between revisions

Thunderbird/Proposal: New Release and Governance Model (view source)

311 bytes added , 19 October 2012

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,627

edits

@@ Line 77: / Line 77: @@
 * Mainstream and ESR releases will not be merged to allow for the intermediate release.
 * We will examine the possibilities for relaxing the rules for stability and security fixes on the ESR branch to allow a greater range of fixes to be landed.
-* Daily, Earlybird and Beta channels will continue to be developed as they are currently, providing the platforms for helping ensure stability for the next feature release, and for Localizers to translate the required strings.
+* Daily, Earlybird and Beta channels will continue to be developed
+** this will continue to provide the platforms for helping ensure stability for the next feature release and
+** for Localizers to translate the required strings
+* Releases on the beta channel will be reduced to one per gecko cycle
+** An additional release may happen if a severe (stability/security) issue affecting beta users is found
+** Additional releases will happen in the two cycles in the run-up to the next feature release to help to ensure stability
-* Need diagram here
+* '''ToDo''': Need diagram here
 Although the intermediate release is not desired at the current time, for an intermediate release to happen, the following would be required: