SeaMonkey:Home Page: Difference between revisions

correct links and referrings to first release, add links to drivers list and project goals
(→‎The plan: Add link to tracking bug)
(correct links and referrings to first release, add links to drivers list and project goals)
Line 16: Line 16:


== The plan ==
== The plan ==
We need to create 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.
We have created a [[SeaMonkey:Project_Organization#SeaMonkey_Drivers|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.


For one thing, we have to get a [[SeaMonkey:1.8 release|1.8 release]] out the door.
Our [[SeaMonkey:Project Goals|Project Goals]] document describes where the project is basically headed.


In preparation for this 1.8 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&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 1.8 release.
For one thing, we have to get a [[SeaMonkey:First Release|first release]] out the door.


[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 initial 1.8 release.
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&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.
 
[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.


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 [https://bugzilla.mozilla.org/show_bug.cgi?id=255807 bug 255807]), preferrably up to the whole XULRunner thingy.
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 [https://bugzilla.mozilla.org/show_bug.cgi?id=255807 bug 255807]), preferrably up to the whole XULRunner thingy.
Line 33: Line 35:
== The team ==
== The team ==


A group of very active SeaMonkey developers has recently gathered on IRC and agreed that we want to have a team of 5-6 drivers who are responsible for project and release mangement. We are almost finished on having that drivers team together and will post a list soon right here.
A group of very active SeaMonkey developers has recently gathered on IRC and agreed on a [[SeaMonkey:Project_Organization#SeaMonkey_Drivers|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.
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.
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits