SeaMonkey:Home Page: Difference between revisions
Pweilbacher (talk | contribs) |
(→Status) |
||
| Line 7: | Line 7: | ||
== Status == | == Status == | ||
The SeaMonkey project released SeaMonkey 1.0 in January 2006 | The SeaMonkey project released SeaMonkey 1.0 in January 2006, SeaMonkey 1.1 in January 2007, and then developed SeaMonkey 2.0 with a final release in October 2009. Security and stability updates are continuing for 2.0, possibly even randomly for 1.1. | ||
[[SeaMonkey:Home Page#Development|Development]] of functionality changes is now done for a SeaMonkey 2.1, planned to be released in the second quarter of 2010. Currently no firm plans do exist for the exact features or Mozilla platform version it will be based on. | |||
For more details on the project status, see [[SeaMonkey:StatusMeetings]]. | For more details on the project status, see [[SeaMonkey:StatusMeetings]]. | ||
Revision as of 14:59, 2 November 2009
 | ||
| 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, SeaMonkey 1.1 in January 2007, and then developed SeaMonkey 2.0 with a final release in October 2009. Security and stability updates are continuing for 2.0, possibly even randomly for 1.1.
Development of functionality changes is now done for a SeaMonkey 2.1, planned to be released in the second quarter of 2010. Currently no firm plans do exist for the exact features or Mozilla platform version it will be based on.
For more details on the project status, see SeaMonkey:StatusMeetings.
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.
See also Release History
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. We need help testing changes for SeaMonkey 1.1.x and SeaMonkey 2.0.
To get started with the project, read the getting involved page and/or join in the developer discussions in mozilla.dev.apps.seamonkey or #seamonkey.
If want to contribute to SeaMonkey localization, read our SeaMonkey:Localization page.
Development
In preparation for "SeaMonkey 2.0", the first step is that we have to get SeaMonkey to use the infrastructure of the new products - see the suiterunner page for more information (a huge part of this has already been done).
The SeaMonkey:New for 2.0 document details the new features we should be picking up for 2.0, these are mainly as a result of the toolkit transition.
We also have a Suite Directory Layout document that describes how the new mozilla/suite/ directory in the Mozilla CVS and comm-central hg repositories should be structured.