Thunderbird/Releases

Point Releases

• Releases/Priority_Ranking (Normal / Medium / High)

Team Members

High/Medium Priority:

• Thunderbird drivers (thunderbird-drivers) to give decision.

Normal:

• Project Lead (TBD).

All Priorities:

	Lead	Backup
Project:	TBD	TBD
Security/Dev:	TBD	TBD
Build:	gozer	gozer
QA:	Tsk	TBD

Release Procedure

1. Create new page on Releases for the point release.
2. Copy Releases/Checklist and link to from page in previous step.
3. Follow steps on Releases/Checklist - relevant owner to strike out each step as it is performed.

TODOs

• Point release and drivers could be a separate groups of people - therefore create a separate list release-drivers? (may be a good idea anyway to separate out the two types of email)
• Do all relevant folks have permissions to access security bugs?
• Do the project leads have un-moderated access to mozilla.announce.prerelease and mozilla.announce?
• Release checklist step "Notify mirrors of beta release - Project lead emails Justin" - need more info.
• AV/firewall vendors - need more info.
• Do relevant folks have access to update website?
• Do we need template announcements?
• How much does Build:ReleasePolicy apply to us? How do we monitor/get details.
• MDC DevNews - are we posting there, if so how?
• Do we post press release to [1] as well as MoMO.com? There have been none there over the last few years... Standard8 to ping ss on this.
• stats info - is this just crash-stats? Standard8 to ping ss.
• Need our own version of How to draft release notes
• How do we get the security centre updated? [2]