Releases/Thunderbird 3.0b2/Post Mortem - Revision history

Dmose: Undo revision 155539 by Dmose (Talk)

2009-07-15T21:14:28Z

Undo revision 155539 by Dmose (Talk)

@@ Line 2: / Line 2: @@
 == What went well ==
 == What could have gone better, and lessons learned ==
 === Leading up to the release ===
 === String Freeze ===
 ===  Code Freeze ===
 === Release Notes ===
 === Build ===
 === QA ===
 === L10n ===
 == Anything else ==
 == Actions ==
 == Attendees ==

Dmose: Replaced content with 'Post Mortem for the Thunderbird release of 3.0b2 == What went well == == What could have gone better, and lessons learned == === Leading …'

2009-07-15T21:09:19Z

Replaced content with 'Post Mortem for the Thunderbird release of 3.0b2 == What went well == == What could have gone better, and lessons learned == === Leading …'

@@ Line 2: / Line 2: @@
 == What went well ==
 == What could have gone better, and lessons learned ==
 === Leading up to the release ===
 === String Freeze ===
 ===  Code Freeze ===
 === Release Notes ===
 === Build ===
 === QA ===
 === L10n ===
 == Anything else ==
 == Actions ==
 == Attendees ==

Wsmwk: /* L10n */ de_DE locale is bad

2009-03-21T14:05:55Z

L10n: de_DE locale is bad

@@ Line 45: / Line 45: @@
 * Lessons learned: Compare-locales (l10n dashboard) does not see everything, especially with regards to the windows installer. Need to watch the tinderboxen as well early on to more effectively communicate necessary fixes to localizers
 * Need to clarify the difference between slushy and firm string freeze. We did string-only landings again. We need to avoid this in the upcoming releases
 == Anything else ==

Gozer: /* Build */

2009-03-04T19:22:33Z

Build

← Older revision		Revision as of 19:22, 4 March 2009
Line 34:		Line 34:
	* <code>--official-branding</code> needs to be watched for more carefully		* <code>--official-branding</code> needs to be watched for more carefully
	* Signing is still blocking on MoCo, need to get that done ourselves		* Signing is still blocking on MoCo, need to get that done ourselves
			* Need a tracking bug for landing on the release branch

	=== QA ===		=== QA ===

Gozer: /* Build */

2009-03-04T18:59:46Z

Build

← Older revision		Revision as of 18:59, 4 March 2009
Line 30:		Line 30:
	=== Build ===		=== Build ===

			* Overall, best build so far.
	* Branding changes could be better automated: {{bug\|481374}}		* Branding changes could be better automated: {{bug\|481374}}
			* <code>--official-branding</code> needs to be watched for more carefully
			* Signing is still blocking on MoCo, need to get that done ourselves

	=== QA ===		=== QA ===

Clarkbw: /* String Freeze */

2009-03-04T18:57:41Z

String Freeze

← Older revision		Revision as of 18:57, 4 March 2009
Line 22:		Line 22:
	*** 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?		* 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 ===		=== String Freeze ===

			* Stronger communication of the [[Thunderbird:Driver_Meetings\|drivers meetings]] decisions

	=== Code Freeze ===		=== Code Freeze ===
	=== Release Notes ===		=== Release Notes ===

Gozer: /* Build */

2009-03-04T17:41:43Z

Build

← Older revision		Revision as of 17:41, 4 March 2009
Line 26:		Line 26:
	=== Release Notes ===		=== Release Notes ===
	=== Build ===		=== Build ===
	Branding changes could be better automated: {{bug\|481374}}
			* Branding changes could be better automated: {{bug\|481374}}

	=== QA ===		=== QA ===

Gozer: /* Build */

2009-03-04T17:31:27Z

Build

← Older revision		Revision as of 17:31, 4 March 2009
Line 25:		Line 25:
	=== Code Freeze ===		=== Code Freeze ===
	=== Release Notes ===		=== Release Notes ===
	=== Build ===		=== Build ===
			Branding changes could be better automated: {{bug\|481374}}

	=== QA ===		=== QA ===
	* Need to avoid mixing Litmus runs and Test Days - as it confuses people. This should be fixed with better communication (see 2.1 above).		* Need to avoid mixing Litmus runs and Test Days - as it confuses people. This should be fixed with better communication (see 2.1 above).

Gozer: /* L10n */

2009-03-04T17:30:11Z

L10n

← Older revision		Revision as of 17:30, 4 March 2009
Line 7:		Line 7:
	* Added 5 locales compared with beta1		* Added 5 locales compared with beta1
	* In general the release schedule worked well for us		* In general the release schedule worked well for us
			* mail/locales/shipped-locales could/should be updated by someone from l10n

	== What could have gone better, and lessons learned ==		== What could have gone better, and lessons learned ==

Sipaq: /* L10n */

2009-03-03T22:16:02Z

L10n

← Older revision		Revision as of 22:16, 3 March 2009
Line 33:		Line 33:
	* release schedule finalization came very late. Would be good to get this fixed early on in the beta3 cycle		* release schedule finalization came very late. Would be good to get this fixed early on in the beta3 cycle
	* Lessons learned: Compare-locales (l10n dashboard) does not see everything, especially with regards to the windows installer. Need to watch the tinderboxen as well early on to more effectively communicate necessary fixes to localizers		* Lessons learned: Compare-locales (l10n dashboard) does not see everything, especially with regards to the windows installer. Need to watch the tinderboxen as well early on to more effectively communicate necessary fixes to localizers
			* Need to clarify the difference between slushy and firm string freeze. We did string-only landings again. We need to avoid this in the upcoming releases

	== Anything else ==		== Anything else ==