SeaMonkey:Home Page: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Added meeting note)
(link to new QA page (old content is there))
Line 22: Line 22:
For one thing, we have to get a [[SeaMonkey:First Release|first release]] out the door.
For one thing, we have to get a [[SeaMonkey:First Release|first release]] out the door.


In preparation for this first release, we need as many testers as possible to download and use [http://www.mozilla.org/releases/ Mozilla 1.8 beta 1] or [http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ recent nightly trunk builds]. Bugs should be reported in [https://bugzilla.mozilla.org/ Bugzilla] (after checking for duplicates) and regressions marked with the ''regression'' keyword. [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=-60d&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Recent (Trunk & unspecified) unconfirmed bugs] should be confirmed or marked as duplicate, works for me, invalid, or wontfix. This way, we'll be able to see what bugs need to be fixed before a first release, and what issues need to be reported in the release notes.
In preparation, we need testers to work on [[SeaMonkey:QA|SeaMonkey QA]] to help improve the quality of this first release.


[https://bugzilla.mozilla.org/show_bug.cgi?id=286066 Bug 286066] has been set up as a tracking bug to help keep track of what needs to be done before the first release.
[https://bugzilla.mozilla.org/show_bug.cgi?id=286066 Bug 286066] has been set up as a tracking bug to help keep track of what needs to be done before the first release.

Revision as of 17:42, 16 March 2005

SeaMonkeylogo.png
Resources
SeaMonkey Homepage
FAQ / Help
Goals
Organization
QA
Supporters
Add-ons
Localization
Reasons
Branding
Release History
Tasks & Projects
IRC Chat Logs
Discussion
Suiterunner

The Mozilla "SeaMonkey" application suite should get its new wiki home here.

Status

The Mozilla Foundation has announced that there won't be any more official releases of the Mozilla Application Suite (codename: SeaMonkey), but they will provide infrastructure for community members who wish to continue development. SeaMonkey survival will need a new team that cares about that product and that will take over the lead for its development.

What we currently need for the survival of this product is some place to turn to for people who want to support us, and a plan for how the immediate future of SeaMonkey should look. Additionally, someone should be the project leader and officially the contact for the "outside world" (MoFo, etc.) on matters that concern the SeaMonkey project. We're still working on that.

Boris Zbarsky has posted an open letter to MoFo signed by a number of interested parties, laying out a community transition plan. MoFo has agreed to support this plan.

MoFo Transition Plan Announcement

Boris Zbarsky's Open Letter

The plan

We have created a seamonkey-drivers group. This group will have final say over which bugs are in and which are out for a particular release (and be the group that has control over the relevant bugzilla flags), will be responsible for finding people to work on the bugs that need to be fixed, etc. We'll also need a mailing list for this group of people.

Our Project Goals document describes where the project is basically headed.

For one thing, we have to get a first release out the door.

In preparation, we need testers to work on SeaMonkey QA to help improve the quality of this first release.

Bug 286066 has been set up as a tracking bug to help keep track of what needs to be done before the first release.

For the future, 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 things of the new apps back to SeaMonkey, but retain what makes us like the suite.

I guess we could do a list here of what's to do and who is working on what.

An overview of some thoughts of what has to be done is available at the user page of Biesi

The team

A group of very active SeaMonkey developers has recently gathered on IRC and agreed on a team of SeaMonkey drivers who are responsible for project and release mangement.

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 people doing QA and regular testing on our product. How those groups will be structured and organized is currently being discussed and we hope to have some information about that soon.

A list of the currently known supporters is kept on a separate page (SeaMonkey:Supporters).

Meetings

The next official meeting on IRC is on Tuesday March 22nd 2005 at 17:00 UTC.