Confirmed users
2,615
edits
No edit summary |
|||
| Line 1: | Line 1: | ||
Post Mortem for the [[Thunderbird]] release of [[Releases/Thunderbird 3.0b3|3.0b3]] | Post Mortem for the [[Thunderbird]] release of [[Releases/Thunderbird 3.0b3|3.0b3]] | ||
([[Thunderbird/StatusMeeting/DialInInfo|DialIn Info]]) | |||
== What went well == | == What went well == | ||
* Lots of good feature and bug work; overall response felt positive | * Lots of good feature and bug work; overall response felt positive | ||
| Line 7: | Line 7: | ||
== What could have gone better, and lessons learned == | == What could have gone better, and lessons learned == | ||
=== Leading up to the release === | === Leading up to the release === | ||
* Weekly milestones may have | * Weekly milestones | ||
* | ** may have helped focus somewhat | ||
** enough overhead that folks didn't find time to keep their bugs up-to-date | |||
** Overall, felt like it wasn't worth it | |||
* Continuous extension of schedule without dates | |||
** Allowed desired for a feature to trump all the advantages of agility | |||
** 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. | * 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. | ||