SeaMonkey:Home Page: Difference between revisions
No edit summary |
m (typo) |
||
| Line 9: | Line 9: | ||
The SeaMonkey project has released [http://www.mozilla.org/projects/seamonkey/releases/ SeaMonkey 1.0] in Janury, 2006, and continues development of that internet application suite in three ways: | The SeaMonkey project has released [http://www.mozilla.org/projects/seamonkey/releases/ SeaMonkey 1.0] in Janury, 2006, and continues development of that internet application suite in three ways: | ||
*First, 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") | *First, 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") | ||
*Second, 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 that, will be released as SeaMonkey 1.1 | *Second, 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 that, will be released as SeaMonkey 1.1 and look and feel the same as 1.0 but with those features added. (This is done on "Mozilla 1.8 branch") | ||
*Third, we are working on migrating the whole application to the new backend framework used by our close relatives Firefox, Thunderbird, etc. and even moving toward using the new "XULRunner" architecture. At the same time we're looking to restructure the SeaMonkey-specific code to be in a common place in a more sensible structure. This will bring lots of new possibilites, like having the new Extension Manager, less development difference between Firefox, Thunderbird and SeaMonkey, a better localization framework ("source L10n") and a theme rework, but it also means some bigger changes in how SeaMonkey's backend behaves. We'll try to retain the feel of the well-known suite though as much as possible. The current working title for a release from that work is "SeaMonkey 1.5", but this is subject to change, and that release is not to be expected before 2007. (This work is happening on "Mozilla trunk") | *Third, we are working on migrating the whole application to the new backend framework used by our close relatives Firefox, Thunderbird, etc. and even moving toward using the new "XULRunner" architecture. At the same time we're looking to restructure the SeaMonkey-specific code to be in a common place in a more sensible structure. This will bring lots of new possibilites, like having the new Extension Manager, less development difference between Firefox, Thunderbird and SeaMonkey, a better localization framework ("source L10n") and a theme rework, but it also means some bigger changes in how SeaMonkey's backend behaves. We'll try to retain the feel of the well-known suite though as much as possible. The current working title for a release from that work is "SeaMonkey 1.5", but this is subject to change, and that release is not to be expected before 2007. (This work is happening on "Mozilla trunk") | ||
Revision as of 19:05, 2 March 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 has released SeaMonkey 1.0 in Janury, 2006, and continues development of that internet application suite in three ways:
- First, 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")
- Second, 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 that, will be released as SeaMonkey 1.1 and look and feel the same as 1.0 but with those features added. (This is done on "Mozilla 1.8 branch")
- Third, we are working on migrating the whole application to the new backend framework used by our close relatives Firefox, Thunderbird, etc. and even moving toward using the new "XULRunner" architecture. At the same time we're looking to restructure the SeaMonkey-specific code to be in a common place in a more sensible structure. This will bring lots of new possibilites, like having the new Extension Manager, less development difference between Firefox, Thunderbird and SeaMonkey, a better localization framework ("source L10n") and a theme rework, but it also means some bigger changes in how SeaMonkey's backend behaves. We'll try to retain the feel of the well-known suite though as much as possible. The current working title for a release from that work is "SeaMonkey 1.5", but this is subject to change, and that release is not to be expected before 2007. (This work is happening on "Mozilla trunk")
History
When announcing in the "transition plan" document that there won't be any more official releases of the Mozilla Application Suite, the Mozilla Foundation promised to still provide the new 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 build the SeaMonkey Council, who 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 resposibilities of certain areas in the project. We also need [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.1' flag has been set up in bugzilla to help keep track of what needs to be done before SeaMonkey 1.0.1. 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.