Releases/Thunderbird 2.0.0.12/Post-Mortem
Jump to navigation
Jump to search
This page is for notes from the Thunderbird 2.0.0.12 post-mortem meeting held on Friday, February 29, 2008 at 10am PST. [1]
Agenda
General questions to think about:
- What did we do right? What worked?
- What did we do wrong? What didn't work?
Specific questions:
- Why, in general, are Thunderbird security releases trailing Firefox security releases (leaving millions of Thunderbird users at risk) by increasingly larger intervals and is anything being done to address that? The problem seems to be getting worse, not better.
- Some data (yanked from the release notes pages for maintenance releases):
- 2.0.0.12: Fx released 7 Feb., Tb release 26 Feb. (19 days)
- 2.0.0.9: Fx released 1 Nov., Tb released 14 Nov. (14 days)
- 2.0.0.6: Fx released 30 July, Tb released 1 Aug. (2 days)
- 2.0.0.5: Fx released 17 July, Tb released 19 July (2 days)
- 2.0.0.4: Fx released 30 May, Tb released 14 June (15 days)
- what are the numbers for TB1.5, especially as we got closer to FF2.0 releases
- Rather than looking back, looking forward: how can we fix it so that Tb can be released simultaneously with Fx, especially when the Fx release involves disclosure of security issues that Tb is vulnerable to? Over time, MoMo staff will be able to help some, but ideally contributors could help as well, and possibly sooner than MoMo staff. It'd be good to come up with a list of specific tasks that people can do to help with the Tb releases. A few things which would be helpful to document:
- Exactly what steps are involved in a branch release
- How many hours of work are involved at each spep
- What specific skills & privs are needed for each step
- Who is willing to coach new folks who are interested in helping out but don't already know what needs doing. It will take more time in the short term, but save time long term.
- When writing the Thunderbird 2.0.0.12 announcement, I included a note about Thunderbird 1.5.0.x no longer being supported. Unfortunately, telling these users to upgrade isn't as simple as saying "Check for Updates". We really need to do a major update to create an easier path for those users. Unlike Firefox, we require fully updated users to download a completely new version from our website.
- no need to wait until 3pm for TB releases. See http://wiki.mozilla.org/Build:ReleasePolicy