This page is for notes from the Thunderbird 184.108.40.206 post-mortem meeting held on Friday, February 29, 2008 at 10am PST. 
- 1 Attendance
- 2 Agenda
- 3 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.
- 4 : Some data (yanked from the release notes pages for maintenance releases):
- 5 : 220.127.116.11: Fx released 7 Feb., Tb release 26 Feb. (19 days)
- 6 : 18.104.22.168: Fx released 1 Nov., Tb released 14 Nov. (14 days)
- 7 : 22.214.171.124: Fx released 30 July, Tb released 1 Aug. (2 days)
- 8 : 126.96.36.199: Fx released 17 July, Tb released 19 July (2 days)
- 9 : 188.8.131.52: Fx released 30 May, Tb released 14 June (15 days)
- 10 : what are the numbers for TB1.5, especially as we got closer to FF2.0 releases
- 11 : 184.108.40.206: Fx released 30 May, Tb released 30 May (0 days)
- 12 : 220.127.116.11: Fx released 23 Feb, Tb released 1 March (6 days)
- 13 : 18.104.22.168: Fx released 19 Dec, Tb released 19 Dec (0 days)
- 14 : 22.214.171.124: Fx released 7 Nov, Tb released 7 Nov (0 days)
- 15 : 126.96.36.199: Fx released 14 Sept, Tb released 14 Sept (0 days)
- 16 : 188.8.131.52: Fx released 27 July, Tb released 27 July (0 days)
- 17 :
- 18 : Answer to both this and #2. We're working on this with MoMess. Part of it is "can we start builds as soon as the Firefox beta period?" This would push up releases by a week at the least. We'll also do timestamps for the next release (184.108.40.206) to get a better idea for what's taking the time and where we can improve.
- 19 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:
- 20 : Exactly what steps are involved in a branch release
- 21 : How many hours of work are involved at each spep
- 22 : What specific skills & privs are needed for each step
- 23 : 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.
- 24 When writing the Thunderbird 220.127.116.11 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.
- 25 : We need to have a meeting to decide when we can do a major update. Sam will schedule one with release-drivers and schrep, if needed.
- 26 no need to wait until 3pm for TB releases. See http://wiki.mozilla.org/Build:ReleasePolicy
- 27 : Sam will note this for future releases. By the time I realized it, it was too late in the process to ship earlier.
- 28 is "pushing to mirrors" enough to tell "PR notification can start"
- 29 : Sam followed up with Melissa and will begin sending notifications to PR when we know what time we're planning on shipping.
- 30 how did website updates go?
- 31 : Updates went much smoother this time than Firefox20012.
- 32 add new release to stats before we ship?
- 33 : This was added to the general checklist late (i.e., after it was copied to the 20012-specific one) but will get done for the next release.
davida, dmose, bsterne, dveditz, ss, joduinn, nthomas, emry, abillings
General questions to think about:
- What did we do right? What worked?
- What did we do wrong? What didn't work?
- Advisory was later than ideal. bsterne will work on getting these out earlier in the future.
- Build hand some one-off issues that were resolved during the process. There were some issues with the uk locale which caused locales needing to be re-packed and a second issue was with the "details" link in the update.