The roads I take...
KaiRo's weBlog
| Zeige Beiträge veröffentlicht im Jänner 2008 und mit "SeaMonkey 2" gekennzeichnet an. Zurück zu allen aktuellen Beiträgen |
3. Jänner 2008
SeaMonkey 2 Alpha Criteria
Since our rework of the SeaMonkey suite to using the "new toolkit" on trunk is making good progress, the SeaMonkey Council has talked about setting up criteria our trunk builds have to meet so we can release a first Alpha for SeaMonkey 2.
The relatively small and compact list of those criteria is:
Being feature-complete or doing any kind of feature or locale freeze is something for the Beta phase, rather than for Alpha.
Point a) in this list mainly means that users of Alphas should be able to utilize AUS for upgrading to later builds, esp. Beta and final builds.
The main requirement for d) is that users who migrated a profile with Alpha don't need further "manual" migration to keep using this profile (or even throw away and re-migrate it) with later builds in the 2.0 series, including final and minor updates.
Things like changing to places history should automigrate existing data, so there's no problem with doing that post-Alpha, a small question may remain open for how to deal with people migrating from Thunderbird and having feeds in those profiles, as we probably want to have them pick those up once we support them, but they may look strange in mailnews currently.
The SeaMonkey Council will start marking Alpha blockers according to that criteria in the next days. Note that minor annoyances probably will not block an Alpha release, though we'd like to see them fixed. We're not targeting a fully cleaned up final release yet, this is still an Alpha and it's neither supposed to be feature-complete nor regression-free, but ready to be tested by a significantly wider range of community members than our usual trunk nightlies.
The relatively small and compact list of those criteria is:
- AUS (automated update service) needs to work,
- L10n builds need to be usable,
- no major broken functionality,
- profiles created or migrated with Alpha need to be in a state that doesn't need re-migration until final.
Being feature-complete or doing any kind of feature or locale freeze is something for the Beta phase, rather than for Alpha.
Point a) in this list mainly means that users of Alphas should be able to utilize AUS for upgrading to later builds, esp. Beta and final builds.
The main requirement for d) is that users who migrated a profile with Alpha don't need further "manual" migration to keep using this profile (or even throw away and re-migrate it) with later builds in the 2.0 series, including final and minor updates.
Things like changing to places history should automigrate existing data, so there's no problem with doing that post-Alpha, a small question may remain open for how to deal with people migrating from Thunderbird and having feeds in those profiles, as we probably want to have them pick those up once we support them, but they may look strange in mailnews currently.
The SeaMonkey Council will start marking Alpha blockers according to that criteria in the next days. Note that minor annoyances probably will not block an Alpha release, though we'd like to see them fixed. We're not targeting a fully cleaned up final release yet, this is still an Alpha and it's neither supposed to be feature-complete nor regression-free, but ready to be tested by a significantly wider range of community members than our usual trunk nightlies.
Von KaiRo, um 18:44 | Tags: Mozilla, release, SeaMonkey, SeaMonkey 2 | 3 Kommentare | TrackBack: 2