Confirmed users
2,615
edits
Releases/Thunderbird 3.0b3/Post Mortem: Difference between revisions
Jump to navigation
Jump to search
Releases/Thunderbird 3.0b3/Post Mortem (view source)
Revision as of 17:18, 17 July 2009
, 17 July 2009→What could have gone better, and lessons learned
| Line 6: | Line 6: | ||
=== Leading up to the release === | === Leading up to the release === | ||
* Having no schedule at all and pushing things week by week without any targets was a disaster for anyone who wants to base things on the same code, especially SeaMonkey. Additionally, experience tends to tell that people bring in things more rapidly when they know firm deadlines. | * Having no schedule at all and pushing things week by week without any targets was a disaster for anyone who wants to base things on the same code, especially SeaMonkey. Additionally, experience tends to tell that people bring in things more rapidly when they know firm deadlines. | ||
* Didn't have explicit discussion about how to hand-off between steps on the checklist; so far this doesn't appear to have caused any problems, but still probably worth doing in the future. | |||
=== String Freeze === | === String Freeze === | ||
*Little time for localizers between firm string freeze and cutoff for L10n builds | * Little time for localizers between firm string freeze and cutoff for L10n builds | ||
*Would be good for localizers to have 2 workdays plus a weekend after firm string freeze and before builds are cut for opting in to L10n (some localizers only have internet access during the week, some can only do work on weekends) | * Would be good for localizers to have 2 workdays plus a weekend after firm string freeze and before builds are cut for opting in to L10n (some localizers only have internet access during the week, some can only do work on weekends) | ||
* KaiRo would propose to make L10n (opt-in) cutoff and firm code freeze align and do firm string freeze at least that period of 2 workdays + weekend before that. (IIRC, this is very similar to what Firefox does and allows us to start all builds, including L10n when firm code freeze is done.) | * KaiRo would propose to make L10n (opt-in) cutoff and firm code freeze align and do firm string freeze at least that period of 2 workdays + weekend before that. (IIRC, this is very similar to what Firefox does and allows us to start all builds, including L10n when firm code freeze is done.) | ||
| Line 19: | Line 19: | ||
=== QA === | === QA === | ||
=== L10n === | === L10n === | ||
== Anything else == | == Anything else == | ||
== Actions == | == Actions == | ||
== Attendees == | == Attendees == | ||