213
edits
(→SeaMonkey 1.0 release plan: update for SeaMonkey 1.0b release) |
|||
| Line 7: | Line 7: | ||
The current plan is to release an Alpha and a Beta release from the Mozilla 1.8 branch on the way to that 1.0 release: | The current plan is to release an Alpha and a Beta release from the Mozilla 1.8 branch on the way to that 1.0 release: | ||
* [http://www.mozilla.org/projects/seamonkey/releases/#1.0a SeaMonkey 1.0 Alpha] was released from Gecko 1.8b4, paralleling the Firefox and Thunderbird 1.5 Beta1 releases done by Mozilla Foundation. While the basic codebase may be more beta than alpha quality, our new release process is not completely settled, we don't have our final [http://www.mozilla.org/projects/seamonkey/artwork.html Artwork] yet and we have no dedicated release machines in place, so it's better to call this an early testing release or "Alpha". | * [http://www.mozilla.org/projects/seamonkey/releases/#1.0a SeaMonkey 1.0 Alpha] was released from Gecko 1.8b4, paralleling the Firefox and Thunderbird 1.5 Beta1 releases done by Mozilla Foundation. While the basic codebase may be more beta than alpha quality, our new release process is not completely settled, we don't have our final [http://www.mozilla.org/projects/seamonkey/artwork.html Artwork] yet and we have no dedicated release machines in place, so it's better to call this an early testing release or "Alpha". | ||
* SeaMonkey 1.0 Beta | * [http://www.mozilla.org/projects/seamonkey/releases/#1.0b SeaMonkey 1.0 Beta] was released from Gecko 1.8, like the Firefox 1.5 release. This testing release also incorporates our new [http://www.mozilla.org/projects/seamonkey/artwork.html Logo Artwork] for the first time. | ||
* SeaMonkey 1.0 is planned to be shipped off the Gecko 1.8.0 branch, which might get a few security/stability fixes, but no big changes from what we shipped with beta. ''We now have [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/ 1.0 nightly builds]; please help us testing them!'' | |||
The release processes are managed by the SeaMonkey Council, Chris Thomas is the release engineer in charge of that process. | The release processes are managed by the SeaMonkey Council, Chris Thomas is the release engineer in charge of that process. | ||
edits