Confirmed users
2,595
edits
SeaMonkey/StatusMeetings/2009-08-25: Difference between revisions
Jump to navigation
Jump to search
SeaMonkey/StatusMeetings/2009-08-25 (view source)
Revision as of 12:33, 25 August 2009
, 25 August 2009→SeaMonkey 2.0 Beta 2
(→IanN) |
Philip Chee (talk | contribs) |
||
| Line 26: | Line 26: | ||
* IanN has started triaging nominations, KaiRo finished them! | * IanN has started triaging nominations, KaiRo finished them! | ||
* Code freeze: '''September 1''' - string freeze ''August 27'' (both 23:59 Pacific) | * Code freeze: '''September 1''' - string freeze ''August 27'' (both 23:59 Pacific). | ||
* Targeted ship date: September 8 (Firefox 3.0.14/3.5.3 are targeted Sep 9) | * Targeted ship date: September 8 (Firefox 3.0.14/3.5.3 are targeted Sep 9). | ||
** Thunderbird is targeting Beta4 release on 22nd September with 11th September for code freeze. | ** Thunderbird is targeting Beta4 release on 22nd September with 11th September for code freeze. | ||
** We need to care that they keep shared code stable during the timeframe we need, and the strings in suite/ need to be frozen during our string freeze, which includes mailnews strings. The code freeze period for us should be fairly short, if we have no blockers left on Sep 1, we can do builds on Sep 2 and unfreeze immediately. The string freeze is the real impact. | ** We need to care that they keep shared code stable during the timeframe we need, and the strings in suite/ need to be frozen during our string freeze, which includes mailnews strings. The code freeze period for us should be fairly short, if we have no blockers left on Sep 1, we can do builds on Sep 2 and unfreeze immediately. The string freeze is the real impact. | ||
| Line 34: | Line 34: | ||
* The API changes of {{bug|474701}} would be nice to get, Lightning uses some part of it, filed {{bug|509324}} for that. | * The API changes of {{bug|474701}} would be nice to get, Lightning uses some part of it, filed {{bug|509324}} for that. | ||
* This is our last beta, and that means that September 1st is also feature freeze for the 2.0 series! Exceptions will only be granted in rare and really-high-value cases. | * This is our last beta, and that means that September 1st is also feature freeze for the 2.0 series! Exceptions will only be granted in rare and really-high-value cases. | ||
* Do we have to look for bugs that may need help making the string freeze? | |||
** If we have more features to land for the 2.0 cycle, we should really get them pushed into the tree now or wait for 2.1, unless they are really high reward and we think we really want them in 2.0. | |||
** Thunderbird can't guarantee that they can hold string freeze past the 2nd. | |||
** suite/ will accept new strings for a while in September, but we want to keep changes small once we're officially feature-frozen next Tuesday. | |||
** If we have all blockers resolved by code freeze next Tuesday, we can start the release process with tagging on Wednesday and once the relbranch is tagged, we can unfreeze. | |||
* Current blockers: status? | * Current blockers: status? | ||
** {{Bug|474709}} Depends on the review, but mcsmurf thinks the patch is good. ''Note:'' has string impact. | |||
** {{Bug|507896}} Should not be that difficult to fix [mcsmurf]. | |||
** {{Bug|505832}} The relevant AMO people have been poked [KaiRo]. | |||
=== SeaMonkey 2.0 Final === | === SeaMonkey 2.0 Final === | ||