Personal tools

SeaMonkey:Home Page

From MozillaWiki

Jump to: navigation, search
Resources
SeaMonkey Homepage
FAQ
Goals
Organization
QA
Supporters
Reasons
Branding
Release History
Future Releases
IRC Chat Logs
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!

Contents

Status

  • Development:
    • SeaMonkey 2.28, currently Trunk
    • SeaMonkey 2.27, currently Aurora
    • SeaMonkey 2.26, currently Beta
  • Stable (receiving security and stability updates):
    • SeaMonkey 2.25, released in March 2014.
  • Historic (not receiving any updates, insecure to use):
    • SeaMonkey 2.24, released in February 2014.
    • SeaMonkey 2.23, released in December 2013.
    • SeaMonkey 2.22, released in October 2013.
    • SeaMonkey 2.21, released in September 2013.
    • SeaMonkey 2.20, released in August 2013.
    • SeaMonkey 2.19, released in July 2013.
    • SeaMonkey 2.18, planned for May 2013. (cancelled)
    • SeaMonkey 2.17, released in April 2013.
    • SeaMonkey 2.16, released in February 2013.
    • SeaMonkey 2.15, released in January 2013.
    • SeaMonkey 2.14, released in November 2012.
    • SeaMonkey 2.13, released in October 2012.
    • SeaMonkey 2.12, released in August 2012.
    • SeaMonkey 2.11, released in July 2012.
    • SeaMonkey 2.10, released in June 2012.
    • SeaMonkey 2.9, released in April 2012.
    • SeaMonkey 2.8, released in March 2012.
    • SeaMonkey 2.7, released in January 2012.
    • SeaMonkey 2.6, released in December 2011.
    • SeaMonkey 2.5, released in November 2011.
    • SeaMonkey 2.4, released in September 2011.
    • SeaMonkey 2.3, released in August 2011.
    • SeaMonkey 2.2, released in July 2011.
    • SeaMonkey 2.1, released in June 2011.
    • SeaMonkey 2.0, first released in October 2009.
    • SeaMonkey 1.1, first released in January 2007.
    • SeaMonkey 1.0, first released in January 2006.

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 2.x.

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

The suiterunner page has information on development that happened for the big platform conversion in SeaMonkey 2.0.

The SeaMonkey:New for 2.0 document details the new features we have been 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.