Confirmed users
2,615
edits
(→L10n) |
No edit summary |
||
| Line 10: | Line 10: | ||
** may have helped focus somewhat | ** may have helped focus somewhat | ||
** enough overhead that folks didn't find time to keep their bugs up-to-date | ** enough overhead that folks didn't find time to keep their bugs up-to-date | ||
** | ** weekly granularity too fine | ||
** extra beta help psychology, in part because we had so much in Tb3 | |||
** limit scope early on | |||
* Continuous extension of schedule without dates | * Continuous extension of schedule without dates | ||
** Allowed desired for a feature to trump all the advantages of agility | ** Allowed desired for a feature to trump all the advantages of agility | ||
| Line 22: | Line 24: | ||
* Very late announcement of final release schedule for localizers (slushy string and code freeze had already gone by) | * Very late announcement of final release schedule for localizers (slushy string and code freeze had already gone by) | ||
=== | === Code Freeze === | ||
=== Release Notes === | === Release Notes === | ||
* Probably missed carrying over important items for b2 | |||
* For beta 4, should include all "What's New" sections from older relnotes in reverse-chronological order. | |||
* Should start on relnotes sooner (at code freeze time? details? need to discuss w/rebron) | |||
=== Build === | === Build === | ||
* should we consider updating install.rdf maxVersion for in-tree extensions (DOMi, Venkman) as part of the release automation? | * should we consider updating install.rdf maxVersion for in-tree extensions (DOMi, Venkman) as part of the release automation? | ||
** Standard8: DOMi is set to 2.1a1pre anyway. | ** Standard8: DOMi is set to 2.1a1pre anyway. | ||
** Standard8: Venkman is set to 3.0. | ** Standard8: Venkman is set to 3.0. | ||
* When requesting bouncer entries, don't forget to ask for complete and partial MARs too | * When requesting bouncer entries, don't forget to ask for complete and partial MARs too (Std8 to talk to gozer) | ||
* Need to remember to clean out previous's version builds from nightly latest/ directories | * Need to remember to clean out previous's version builds from nightly latest/ directories | ||
* <code>/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude</code> needs to be modified to include the new release for mirrors to pick it up | * <code>/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude</code> needs to be modified to include the new release for mirrors to pick it up | ||
=== QA === | === QA === | ||
* difficult to mobilize Community : | * difficult to mobilize Community : | ||
| Line 66: | Line 70: | ||
*** A couple of days later (assuming no major issues), make updates automatic. | *** A couple of days later (assuming no major issues), make updates automatic. | ||
** Note, RCs get released on beta channel. Final we can do similar, but leave the automatic update a bit longer if we want (e.g. to first point release). | ** Note, RCs get released on beta channel. Final we can do similar, but leave the automatic update a bit longer if we want (e.g. to first point release). | ||
* Important to communicate 1.9.2 plans clearly and loudly quickly after 3.0 release so (eg enterprise customers) can react to 3.0 release in an informed manner | |||
*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 | *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 == | == Actions == | ||
== Attendees == | == Attendees == | ||
Standard8, _Tsk_, sipaq, dmose | |||