Releases/Thunderbird 3.1a1/Post Mortem
From MozillaWiki
Post Mortem for the Thunderbird release of 3.0b4 (DialIn Info)
Contents
What went well
- No big patches just before code freeze.
- Quality seemed good
What could have gone better, and lessons learned
- We don't have much uptake (~100 users, claims our nightly metric)
- TODO (dmose):
ping deinspanjer to see if we can get the nightly reports split up into AUS channels(status: bug 545034 filed) - TODO (_Tsk_):
blog/message asking for testers to use 3.1 nightlies, even at the expense of 3.2 nightly testers
- TODO (dmose):
Leading up to the release
- More driving earlier on (in progress for beta 1)
- already in progress for b1
- beta 1 to slip a little, if necessary another beta will be added
String Freeze
- No l10n dashboard. From Sipaq: Mid-term we should talk to Pike (and Seth?) about the possibility of giving Gozer admin rights on the l10n dashboard, so that we do not depend solely on Axel for setting up new l10n targets for us.
- We now have one for 1.9.2?
- TODO (dmose): talk to Sipaq/Axel about getting access for gozer (status: emailed sipaq);
- should we consider running our own again?
Code Freeze
- package-compare is undocumented and how to use it is mostly inside Standard8 and philor's heads
- filed as bug 543248; marked as wanted-thunderbird+
- release checklist modified to point to User:Standard8#package-compare_notesfor interim use
Release Notes
- rebron to try sooner for beta 1
- going forward will be easier because branding stuff more stable, processes more templated
Build
- packaging OS X build as Lanikai failed; gozer had to do a hand hack. has been filed. Still need to get it in the right product, assigned to someone, and blocking 3.1b1.
- last minute changes generally cause trouble
- Deciding to go with l10n repacks for build2 was a last-minute decision that ended up causing some delays, combined with the previous issue
- Future plan: be more conservative late in future cycles
QA
- Schedule collision with end of 3.0.x and start of 3.1
- Need to plan better and have a better visibility on schedules
L10n
- Covered previous parts of post-mortem
- New automated system integrated into dashboard to be used soon
- TODO (sipaq): talk to Pike, decide if we can/should use for b1, notify drivers
Anything else
Actions
Attendees
rebron, dmose, _Tsk_, gozer, Standard8