SeaMonkey:Home Page: Difference between revisions
(→How to help: update for SeaMonkey 1.0.2) |
m (→Status: link to the branch plan, seems useful.) |
||
| Line 10: | Line 10: | ||
*Firstly, SeaMonkey 1.0.x releases will be security and stability updates to SeaMonkey 1.0 (happening on the so-called "Mozilla 1.8.0 branch"). | *Firstly, SeaMonkey 1.0.x releases will be security and stability updates to SeaMonkey 1.0 (happening on the so-called "Mozilla 1.8.0 branch"). | ||
*Secondly, work is being done to add [https://bugzilla.mozilla.org/show_bug.cgi?id=315312 some new features] to the suite without changing the basis that SeaMonkey 1.0 built upon. The result of this work will be released as SeaMonkey 1.1, which will look and feel the same as 1.0 except for the newly added features. (This is done on the "Mozilla 1.8 branch".) | *Secondly, work is being done to add [https://bugzilla.mozilla.org/show_bug.cgi?id=315312 some new features] to the suite without changing the basis that SeaMonkey 1.0 built upon. The result of this work will be released as SeaMonkey 1.1, which will look and feel the same as 1.0 except for the newly added features. (This is done on the "Mozilla 1.8 branch".) | ||
*Finally, we are working on migrating the entire application to the new backend framework used by our close relatives Firefox, Thunderbird, etc., and are even moving toward using the new | *Finally, we are working on migrating the entire application to the new backend framework used by our close relatives Firefox, Thunderbird, etc., and are even moving toward using the new [[XULRunner]] architecture. At the same time we're looking to restructure the SeaMonkey-specific code, aiming to have this code live in a more sensible structure in one common location. This work will mean less development differences between Firefox, Thunderbird and SeaMonkey, and will result in lots of new possibilites, such as having the new Extension Manager, a better localization framework ("source L10n") and a theme rework, but it will also mean some bigger changes in how SeaMonkey's backend behaves. Despite this, we'll try to retain the feel of the well-known suite as much as possible. The current working title for a release from that work is "SeaMonkey 1.5" (subject to change) with a release not to be expected before 2007. (This work is happening on "Mozilla trunk".) | ||
([[Global:1.9 Trunk 1.8 Branch Plan]] explains the trunk and branches.) | |||
== History == | == History == | ||
Revision as of 02:45, 18 April 2006
 | ||
| Resources | ||
|---|---|---|
| SeaMonkey Homepage | ||
| FAQ / Help | ||
| Goals | ||
| Organization | ||
| QA | ||
| Supporters | ||
| Add-ons | ||
| Localization | ||
| Reasons | ||
| Branding | ||
| Release History | ||
| Tasks & Projects | ||
| ||
| Discussion | ||
| Suiterunner |
This Mozilla Wiki section covers documents about the SeaMonkey Project, which develops an "all-in-one internet application suite", based on code of the previous Mozilla Application Suite.
For quick answers to common questions, please explore the SeaMonkey FAQ!
Status
The SeaMonkey project released SeaMonkey 1.0 in January 2006, and will now continue development of that internet application suite in three ways:
- Firstly, SeaMonkey 1.0.x releases will be security and stability updates to SeaMonkey 1.0 (happening on the so-called "Mozilla 1.8.0 branch").
- Secondly, work is being done to add some new features to the suite without changing the basis that SeaMonkey 1.0 built upon. The result of this work will be released as SeaMonkey 1.1, which will look and feel the same as 1.0 except for the newly added features. (This is done on the "Mozilla 1.8 branch".)
- Finally, we are working on migrating the entire application to the new backend framework used by our close relatives Firefox, Thunderbird, etc., and are even moving toward using the new XULRunner architecture. At the same time we're looking to restructure the SeaMonkey-specific code, aiming to have this code live in a more sensible structure in one common location. This work will mean less development differences between Firefox, Thunderbird and SeaMonkey, and will result in lots of new possibilites, such as having the new Extension Manager, a better localization framework ("source L10n") and a theme rework, but it will also mean some bigger changes in how SeaMonkey's backend behaves. Despite this, we'll try to retain the feel of the well-known suite as much as possible. The current working title for a release from that work is "SeaMonkey 1.5" (subject to change) with a release not to be expected before 2007. (This work is happening on "Mozilla trunk".)
(Global:1.9 Trunk 1.8 Branch Plan explains the trunk and branches.)
History
In 2005, the Mozilla Foundation released a "transition plan" for the Mozilla Application Suite, in which they announced that there won't be any more official releases of the Mozilla Application Suite. At the same time they promised to still provide the newly created, mozilla.org-hosted, SeaMonkey project with needed infrastructure to do further development on the suite code and release it under the project's new name.
The team
A group of very active SeaMonkey developers make up the SeaMonkey Council, which is responsible for project and release management.
That doesn't mean we don't need an even bigger group of developers working on the product or taking responsibilities of certain areas in the project. We also need people doing QA and regular testing on our product. The development community of SeaMonkey is structured into project areas which cover different parts of the SeaMonkey project. Many of those still need help from more developers; if you want to lend us a hand there, please contact seamonkey-council@mozilla.org.
Here is a page with a list of the currently known supporters.
How to help
Our Project Goals document describes where the project is basically headed.
You can help by working on SeaMonkey QA as you use SeaMonkey.
Several bugzilla flags track iussues that need to be fixed for our upcoming releases:
A 'blocking-seamonkey1.0.2' flag has been set up in bugzilla to help keep track of what needs to be done before SeaMonkey 1.0.2. You can create your own query with this flag, or view the open approved bugs and yet to be approved bugs blocking the release.
A 'blocking-seamonkey1.1a' flag has been set up in bugzilla to help keep track of what needs to be done before SeaMonkey 1.1a. You can create your own query with this flag, or view the open approved bugs and yet to be approved bugs blocking the release.
Development
In preparation for "SeaMonkey 1.5", the first step is that we have to get SeaMonkey to use the infrastructure of the new products (for example the toolkit which is discussed in bug 255807), preferrably up to the whole XULRunner thingy. We also should port a few features of the new apps back to SeaMonkey, but retain what makes us like the suite.
The SeaMonkey:Toolkit_Transition document describes what's planned for that big transition.
We also have a SeaMonkey:Suite_Directory_Layout document that describes how the new mozilla/suite/ directory in the CVS repository should be structured.
Meetings
There was a Town Hall meeting at IRC on Wednesday July 6th 2005 at 15:00 UTC (log).
If you have agenda items, please e-mail Alex Vincent with your ideas.