Thunderbird/New Release and Governance Model: Difference between revisions

Initial cuts
(Created page with "Mozilla is focusing a lot of its efforts towards important web and mobile projects, while Thunderbird remains a pure desktop only email client. We have come to the conclusion tha...")
 
(Initial cuts)
Line 5: Line 5:
In order to manage these two perspectives, we are proposing to adapt the Thunderbird release and governance model in a way that allows both ongoing security and stability maintenance as well as community driven innovations for the product. We are opening this plan for discussion to individuals and organizations interested in maintaining and advancing Thunderbird in the future. We are looking for your feedback, comments and suggestions to refine and adapt the plan in the best possible way.
In order to manage these two perspectives, we are proposing to adapt the Thunderbird release and governance model in a way that allows both ongoing security and stability maintenance as well as community driven innovations for the product. We are opening this plan for discussion to individuals and organizations interested in maintaining and advancing Thunderbird in the future. We are looking for your feedback, comments and suggestions to refine and adapt the plan in the best possible way.


= Proposal=
= Highlights =
== Highlights ==
== Thunderbird and Thunderbird ESR ==
=== Thunderbird and Thunderbird ESR ===
There are currently two editions of Thunderbird: 'Thunderbird' and 'Thunderbird ESR'. Both will be maintained and based on the same Gecko engine release. Only 'Thunderbird' is affected by the change:
There are currently two editions of Thunderbird: 'Thunderbird' and 'Thunderbird ESR'. Both will be maintained and based on the same Gecko engine release. Only 'Thunderbird' is affected by the change:
* A new release of Thunderbird ESR will be available on November 20th, 2012. As defined in the Thunderbird ESR plan (http://www.mozilla.org/thunderbird/organizations/faq/),  it will inherit the then-current Thunderbird feature-set. This release will be updated every six weeks, for the duration of the ESR cycle to ensure the best possible security and stability for organizations.
* A new release of Thunderbird ESR will be available on November 20th, 2012. As defined in the Thunderbird ESR plan (http://www.mozilla.org/thunderbird/organizations/faq/),  it will inherit the then-current Thunderbird feature-set. This release will be updated every six weeks, for the duration of the ESR cycle to ensure the best possible security and stability for organizations.
* At the same time, Thunderbird will be released with the same feature set as Thunderbird ESR and will be updated every six-weeks for security and stability. However, and contrary to Thunderbird ESR, Thunderbird feature set might evolve over time and solely based on the availability of community contributions.
* At the same time, Thunderbird will be released with the same feature set as Thunderbird ESR and will be updated every six-weeks for security and stability. However, and contrary to Thunderbird ESR, Thunderbird may include an additional release during the ESR timeframe which would include extra features.


The proposed plan should therefore have no impact in the way individuals and organizations use the product and obtain updates.
The plan should therefore have no impact in the way individuals and organizations use the product and obtain updates.


=== Governance model ===
== Governance model ==
Thunderbird will be driven by a lightweight structure, focusing on producing security updates and suited to welcome community contributed innovations:
Thunderbird will be driven by a lightweight structure, focusing on producing security updates and suited to welcome community contributed innovations:


* Thunderbird modules owners (https://wiki.mozilla.org/Modules) will remain in charge of their module and will allow community contributions innovation on their own merits. Module ownership is open to any contributor and can evolve over time.
* Thunderbird modules owners (https://wiki.mozilla.org/Modules) will remain in charge of their module and will allow community contributions innovation on their own merits. Module ownership is open to any contributor and can evolve over time.


* A Release Drivers team will produce the Thunderbird updates every six weeks and work with module owners on the planning and integration of the community contributed innovations.<br/><br/>
* A Release Drivers team will produce the Thunderbird updates every six weeks and work with module owners on the planning and integration of the community contributed innovations.


* Mozilla will continue to provide paid staff, logistics and infrastructure for the release drivers team to produce updates and new releases with the same level of quality than today. Support will continue to be provided by the Thunderbird community and Mozilla will continue to provide the required infrastructure.<br/>
* Mozilla will continue to provide paid staff, logistics and infrastructure for the release drivers team to produce updates and new releases with the same level of quality than today. Support will continue to be provided by the Thunderbird community and Mozilla will continue to provide the required infrastructure.


=== Timeline and getting involved ===
= Governance =
We are looking forward to getting your questions and comments on this plan. We would like to refine it throughout the summer so we can discuss the final details at the beginning of September 2012. If you want to be involved in this discussion, please use the tb-planning mailing list (https://wiki.mozilla.org/Thunderbird/tb-planning) as a discussion forum.
 
= Details =
{{Warning|This document is work in progress.}}
 
''
For the sake of practicality and during the discussion period,
* Feel free to document the below sections with topics you want to be addressed.
* Among the needed information, we need to document the questions we have and questions regarding Mozilla participation in this section.
* Etherpad is probably more practical to jot ideas down than the Wiki. Therefore, it might be useful to create one for each of the below sections to allow contributors to collaborate towards identifying the needs and their solutions.
''
 
Each section below addresses one aspect of maintaining and building Thunderbird. They reflect the discussions that have taken place with volunteers and Mozilla employees during the summer of 2012.
 
== Governance ==
Link to etherpad: https://etherpad.mozilla.org/tb-governance
Link to etherpad: https://etherpad.mozilla.org/tb-governance


Line 86: Line 70:


The decision for the intermediate release is made by the module owners, but signed off by the release drivers.
The decision for the intermediate release is made by the module owners, but signed off by the release drivers.
Link to etherpad: https://etherpad.mozilla.org/tb-releases


== Localization ==
== Localization ==
Line 99: Line 81:
* '''ToDo''':
* '''ToDo''':
** We need to complete the documentation for management of L10n (product & website)
** We need to complete the documentation for management of L10n (product & website)
Link to etherpad: https://etherpad.mozilla.org/tb-localization


== AMO ==
== AMO ==
Line 106: Line 86:
* Add-on Review mechanisms to continue working as they are with the AMO editor team
* Add-on Review mechanisms to continue working as they are with the AMO editor team
* Compatibility bumps still need to be done per release ([[Thunderbird/Release_Driving/Rapid_Release_Activities/Compatibility_Bump|partial documentation complete]])
* Compatibility bumps still need to be done per release ([[Thunderbird/Release_Driving/Rapid_Release_Activities/Compatibility_Bump|partial documentation complete]])
Link to etherpad: https://etherpad.mozilla.org/tb-amo


== Quality Assurance ==
== Quality Assurance ==
Line 114: Line 92:
* This is already a community-involved process
* This is already a community-involved process
* Todo: Document how bugs get from triage to developers
* Todo: Document how bugs get from triage to developers
Link to etherpad: https://etherpad.mozilla.org/tb-qa


== Services & Web Sites ==
== Services & Web Sites ==
Line 124: Line 100:
* ispdb expected to be brought up to replace the static files for autoconfig.
* ispdb expected to be brought up to replace the static files for autoconfig.
* Other sites expected to be low maintenance, but change processes to be documented.
* Other sites expected to be low maintenance, but change processes to be documented.
Link to etherpad: https://etherpad.mozilla.org/tbsites


== Support ==
== Support ==
Line 135: Line 109:
* Roland continues to lead support
* Roland continues to lead support
** Will still produce support reports 48 hours after release and the Monday after a release
** Will still produce support reports 48 hours after release and the Monday after a release
Link to etherpad: https://etherpad.mozilla.org/tb-support


== Docs ==
== Docs ==
Line 144: Line 116:
* Need to ensure that the necessary documentation for releases is co-ordinated with release drivers
* Need to ensure that the necessary documentation for releases is co-ordinated with release drivers
* TBD: who is responsible for approving KB contributions?
* TBD: who is responsible for approving KB contributions?
Link to etherpad: https://etherpad.mozilla.org/tb-docs
== Engagement ==
Link to Etherpad: https://etherpad.mozilla.org/QNUuZdC0pU


== Lightning ==
== Lightning ==
Line 156: Line 123:
* There may be a benefit during upgrades, as fewer binary-compatibility issues will arise.
* There may be a benefit during upgrades, as fewer binary-compatibility issues will arise.
* Daily/Earlybird builds have to be monitored more closely, as they are the only notice for major platform changes that might affect Lightning.
* Daily/Earlybird builds have to be monitored more closely, as they are the only notice for major platform changes that might affect Lightning.
Link to etherpad: https://etherpad.mozilla.org/tb-lightning
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627

edits