canmove, Confirmed users
2,081
edits
Releases/Thunderbird 3.0b2/Post Mortem: Difference between revisions
Releases/Thunderbird 3.0b2/Post Mortem (view source)
Revision as of 18:10, 28 February 2009
, 28 February 2009no edit summary
No edit summary |
|||
| Line 3: | Line 3: | ||
Post Mortem for the [[Thunderbird]] release of [[Releases/Thunderbird 3.0b2|3.0b2]] | Post Mortem for the [[Thunderbird]] release of [[Releases/Thunderbird 3.0b2|3.0b2]] | ||
== | == What went well == | ||
== What could have gone better, and lessons learned == | |||
In reference to the [[Thunderbird:Thunderbird 3.0b2]] page. | === Leading up to the release === | ||
* In reference to the [[Thunderbird:Thunderbird 3.0b2|Development Page]] page. | |||
* Weekly milestones are necessary | ** Weekly milestones are necessary | ||
** Create a milestone for every week in release cycle | *** Create a milestone for every week in release cycle | ||
** Name milestones: ${REL}week${NUM} ex: b2week1, b2week2, etc | *** Name milestones: ${REL}week${NUM} ex: b2week1, b2week2, etc | ||
** Plan landing of items (features/bugs) in each week | *** Plan landing of items (features/bugs) in each week | ||
** Set status whiteboard of bugs with milestone names (makes them searchable) | *** Set status whiteboard of bugs with milestone names (makes them searchable) | ||
** Work with Q/A to plan sessions testing milestone one week after it lands | *** Work with Q/A to plan sessions testing milestone one week after it lands | ||
** Create search links for each week milestone | *** Create search links for each week milestone | ||
* Release dates should have indicator of strength | ** Release dates should have indicator of strength | ||
** Something like keywords '''strong''', '''weak''', or '''likely to slip''' to communicate how solid the dates are at this point | *** Something like keywords '''strong''', '''weak''', or '''likely to slip''' to communicate how solid the dates are at this point | ||
* should release process planning meeting be removed from [[Releases/Thunderbird 3.0b2|3.0b2]]? (hasn't been done for last 2 releases) Should it simply be replaced with references to prior releases' postmortems? | |||
=== String Freeze === | |||
=== Code Freeze === | |||
=== Release Notes === | |||
=== Build === | |||
=== QA === | |||
== Anything else == | |||
* need to firm up crash-stats.m.c update step, seems to be insufficient to ask for adding the release and next development release. ref {{bug|480728}} MTBF missing Thunderbird 3.0b2 milestone, and development 3.0b3pre & 3.1a1pre // 3.0b2 topcrash no results | |||
== Actions == | |||
== Attendees == | |||