SeaMonkey/StatusMeetings/2011-06-28: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 32: Line 32:
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).
* The correct version numbers are now on the release train.
* The correct version numbers are now on the release train.
* We'll probably need an update on the AUS server to support aurora nightlies correctly (KaiRo will probably do this sometime this week). '''Status/update?'''
* <s>We'll probably need an update on the AUS server to support aurora nightlies correctly.
* We'll need to ensure that we set the correct channel for aurora nightlies. Leaving this to Callek.  '''Status/update?'''
* We'll need to ensure that we set the correct channel for aurora nightlies. Leaving this to Callek.</s>
** AUS is fine. It's the buildbot stuff and Callek needs to deal with it.
* ''We released 2.2b1.''
* ''We released 2.2b1.''
** As FF shipped 5.0, we should be concentrating on getting a 2.2 out the door, especially as it has some fixes for issues in 2.1.
** As FF shipped 5.0, we should be concentrating on getting a 2.2 out the door, especially as it has some fixes for issues in 2.1.
* 2.3 should go into beta in 2-3 weeks (not sure when exactly the uplift is, might actually be 3) and then we'll have 6 weeks to release.
* 2.3 should go into beta in 2-3 weeks (not sure when exactly the uplift is, might actually be 3) and then we'll have 6 weeks to release.
* status-seamonkey2.2 flags still haven't been set up.
* Bug authors have been doing a fairly good job of requesting relevant approvals for the comm-aurora/beta


=== SeaMonkey 2.1 ===
=== SeaMonkey 2.1 ===
Confirmed users
2,595

edits

Navigation menu