MozillaWiki - User contributions [en]

SeaMonkey/StatusMeetings/2008-12-16

2008-12-16T06:31:22Z

Ajschult:

[[SeaMonkey:StatusMeetings:2008-12-02|« last meeting]] | [[SeaMonkey:StatusMeetings|index]]

'''SeaMonkey Meeting Details'''

* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=16&month=12&year=2008&hour=13&min=0&sec=0&p1=0 December 16, 2008, 13:00 UTC]
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]

== Agenda ==
* Who's taking minutes?

=== Action Items ===
(who needs to do what that hasn't been recorded in a bug)
* Summarize SeaMonkey vision thread to useful goals, post them, and get a final series of comments before deciding on them in the Council [KaiRo]

=== SeaMonkey 2 Alpha 2 ===

[http://www.seamonkey-project.org/releases/seamonkey2.0a2/ Has been released.]

Thanks to everyone who helped achieving that!

Any feedback we should care about?

=== SeaMonkey 2 Alpha 3 ===

Bug Queries

[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%2B open blockers]
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%2B all blockers]
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%3F blocker requests]

* Plans for freeze?
** Thunderbird probably freezing on Jan 29, would that be a good target for us?

=== Longer-Term SeaMonkey 2 Planning ===

[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2%2B open wanted]
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2%3F wanted requests]

Major wanted/needed features:

* {{bug|381157}} Download manager
** Has some more progress, delayed from some personal build issues (upgraded MozBuild and ran into conflicts with GDesktop I didn't expect) and my patch I was going to attach came at a time tree was red (rebuilding now and will get new patch up this week) finally.
* {{bug|390025}} Kill-wallet (password manager)
** status/progress?
* {{bug|382187}} Places history
** '''landed for alpha3'''.
** Some followups filed, some already being actively worked on.
* {{bug|36810}} Session restore
** '''Still''' waiting for review - Andrew promised he'll have son time within a week and should be able to look into it.
* {{bug|394288}} / {{bug|413385}} Toolbar customization.
** status/progress?
** Toolkit {{bug|407725}} is in mozilla-central and 1.9.1 now and seems to stay for good now.
* {{bug|456757}} Modern theme update
** status/progress?
* {{bug|460699}} Make the default theme look better on mac
** Work in slowly progress. A new set of toolbaricons, based on the old ones, are attached in the bug. Lots of css work left, though.
* {{bug|454847}} Fishcam update
** Waiting on new http://www.fishcam.com/ (by the original fishcam creator) might just be what we are looking for.
* {{bug|410613}} OpenSearch
** '''helpwanted'''
* Handling {{bug|420506}} Thunderbird kill-rdf
** {{bug|460952}} Ensure Thunderbird kill-rdf doesn't break SeaMonkey
*** status/progress?
** {{bug|460953}} Port jminta's kill-rdf to SeaMonkey where applicable
*** status/progress?
* {{bug|415372}} Implement Feed Preview
** '''helpwanted''' - Callek to concentrate on download manager instead.
*** Callek still promising fast reviews, since he knows the general lay of the Firefox code and how it all ties together fairly well.
* {{bug|460960}} Port Thunderbird tabbed interface to MailNews
*** status/progress?

=== Roundtable ===

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

==== ajschult ====
* Will be gone Dec 21-31

==== biesi ====
==== Callek ====
* More work on DLMGR, I have progress dialoges (roughly) working locally -- I think (see Build issues comments above)
* After briefly talking with KaiRo I decided to put the plate I was saving for feed Preview back in the cabinet for someone else to take... I will provide all the help I can here (including fast reviews! something hard to come by)... See my newsgroup post for more.
* Various discussions regarding longer term planning and testing infrastructure.

==== IanN ====
==== KaiRo ====
* As always, [http://home.kairo.at/blog/ my blog] has more detailed status about my work.

==== mcsmurf ====
==== Misak ====
* {{bug|36810}} (session restore).
* {{bug|459550}} (Port Bug 448976 (turn the Session Restore prompt into an error page) to SeaMonkey).
* {{Bug|425480}} (non-ASCII characters should be decoded in the urlbar).
* {{Bug|455877}} (port Bug 254714 to SeaMonkey).
* Tests for cert error page.

==== Mnyromyr ====
==== MReimer ====
==== Neil ====
==== Ratty ====
==== sgautherie ====
==== Standard8 ====
==== stefanh ====
* Started to work a bit on bug {{bug|460699}}. Fixed a couple of minor ui bugs.
==== wladow ====

=== Any other business? ===

* ?

SeaMonkey/StatusMeetings/2008-12-16

2008-12-16T06:30:49Z

Ajschult:

[[SeaMonkey:StatusMeetings:2008-12-02|« last meeting]] | [[SeaMonkey:StatusMeetings|index]]

'''SeaMonkey Meeting Details'''

* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=16&month=12&year=2008&hour=13&min=0&sec=0&p1=0 December 16, 2008, 13:00 UTC]
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]

== Agenda ==
* Who's taking minutes?

=== Action Items ===
(who needs to do what that hasn't been recorded in a bug)
* Summarize SeaMonkey vision thread to useful goals, post them, and get a final series of comments before deciding on them in the Council [KaiRo]

=== SeaMonkey 2 Alpha 2 ===

[http://www.seamonkey-project.org/releases/seamonkey2.0a2/ Has been released.]

Thanks to everyone who helped achieving that!

Any feedback we should care about?

=== SeaMonkey 2 Alpha 3 ===

Bug Queries

[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%2B open blockers]
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%2B all blockers]
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a3%3F blocker requests]

* Plans for freeze?
** Thunderbird probably freezing on Jan 29, would that be a good target for us?

=== Longer-Term SeaMonkey 2 Planning ===

[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2%2B open wanted]
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2%3F wanted requests]

Major wanted/needed features:

* {{bug|381157}} Download manager
** Has some more progress, delayed from some personal build issues (upgraded MozBuild and ran into conflicts with GDesktop I didn't expect) and my patch I was going to attach came at a time tree was red (rebuilding now and will get new patch up this week) finally.
* {{bug|390025}} Kill-wallet (password manager)
** status/progress?
* {{bug|382187}} Places history
** '''landed for alpha3'''.
** Some followups filed, some already being actively worked on.
* {{bug|36810}} Session restore
** '''Still''' waiting for review - Andrew promised he'll have son time within a week and should be able to look into it.
* {{bug|394288}} / {{bug|413385}} Toolbar customization.
** status/progress?
** Toolkit {{bug|407725}} is in mozilla-central and 1.9.1 now and seems to stay for good now.
* {{bug|456757}} Modern theme update
** status/progress?
* {{bug|460699}} Make the default theme look better on mac
** Work in slowly progress. A new set of toolbaricons, based on the old ones, are attached in the bug. Lots of css work left, though.
* {{bug|454847}} Fishcam update
** Waiting on new http://www.fishcam.com/ (by the original fishcam creator) might just be what we are looking for.
* {{bug|410613}} OpenSearch
** '''helpwanted'''
* Handling {{bug|420506}} Thunderbird kill-rdf
** {{bug|460952}} Ensure Thunderbird kill-rdf doesn't break SeaMonkey
*** status/progress?
** {{bug|460953}} Port jminta's kill-rdf to SeaMonkey where applicable
*** status/progress?
* {{bug|415372}} Implement Feed Preview
** '''helpwanted''' - Callek to concentrate on download manager instead.
*** Callek still promising fast reviews, since he knows the general lay of the Firefox code and how it all ties together fairly well.
* {{bug|460960}} Port Thunderbird tabbed interface to MailNews
*** status/progress?

=== Roundtable ===

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

==== ajschult ====
Will be gone Dec 21-31

==== biesi ====
==== Callek ====
* More work on DLMGR, I have progress dialoges (roughly) working locally -- I think (see Build issues comments above)
* After briefly talking with KaiRo I decided to put the plate I was saving for feed Preview back in the cabinet for someone else to take... I will provide all the help I can here (including fast reviews! something hard to come by)... See my newsgroup post for more.
* Various discussions regarding longer term planning and testing infrastructure.

==== IanN ====
==== KaiRo ====
* As always, [http://home.kairo.at/blog/ my blog] has more detailed status about my work.

==== mcsmurf ====
==== Misak ====
* {{bug|36810}} (session restore).
* {{bug|459550}} (Port Bug 448976 (turn the Session Restore prompt into an error page) to SeaMonkey).
* {{Bug|425480}} (non-ASCII characters should be decoded in the urlbar).
* {{Bug|455877}} (port Bug 254714 to SeaMonkey).
* Tests for cert error page.

==== Mnyromyr ====
==== MReimer ====
==== Neil ====
==== Ratty ====
==== sgautherie ====
==== Standard8 ====
==== stefanh ====
* Started to work a bit on bug {{bug|460699}}. Fixed a couple of minor ui bugs.
==== wladow ====

=== Any other business? ===

* ?

SeaMonkey/StatusMeetings/2008-07-15

2008-07-15T05:52:17Z

Ajschult: /* Roundtable */

[[SeaMonkey:StatusMeetings:2008-07-01|« last meeting]] | [[SeaMonkey:StatusMeetings|index]]

'''SeaMonkey Meeting Details'''

* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=15&month=7&year=2008&hour=12&min=0&sec=0&p1=0 July 15, 2008, 12:00 UTC]
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]

== Agenda ==

=== Action Items ===

* ?

=== SeaMonkey 2 Alpha ===

[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a1%2B all blockers]
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a1%3F blocker requests]

* {{bug|381157}} download manager (soft blocker)
** Status/Progress?
* {{bug|390025}} kill-wallet (password manager) (soft blocker)
** Status/Progress?
* {{bug|394522}} prefwindow move (hard blocker)
** Status/Progress - bugs have now been logged for any outstanding prefpanes that still need migrating. A number have yet to be assigned (1 Browser, 1 MailNews, 3 Privacy/Security), the rest is work in progress or even under review.

=== Longer-Term SeaMonkey 2 Planning ===

* We'll be building up and moving to the [http://hg.mozilla.org/comm-central/ comm-central] hg repository soon, see {{bug|437643}} - basically only waiting for Thunderbird to cut alpha2 and reviews for the build system patches in {{bug|444686}}
* Mozilla 1.9.1 platform is probably going to feature-freeze in mid August (beta1), anything we want to get in there should be done before that
* Is someone, preferably who's not working on any major SM2 thing right now, up for porting the history UI to places? (backend works fine with --enable-places)
* typeaheadfind will still be pulled from CVS when we switch to comm-central, blocks us from doing static or libxul builds and duplicates code that toolkit has - this badly needs some love

=== Next Status Meeting / Firefox Plus Summit ===

* Next meeting would be on July 29, which is during [[Summit2008|Firefox Plus Summit]]
* A few core SeaMonkey contributors are there and in Pacific timezone because of that - who exactly is there?
* What to do about that meeting?
* Can we do a dinner/post-dinner SeaMonkey come-together at the Summit? Would be nice to gather SeaMonkey people in one place some time in this week.

=== Roundtable ===

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status)

* ajschult
** QA good for 1.1.11 release
* biesi
* Callek
** Still working on DLMGR, last two weeks not much progress here.
** Performed reviews on build system work for comm-central, and assisted in related discussions.
** Prepared blog announcement for 1.1.11 release.
* IanN
** Keeping Mnyromyr and Neil busy with pref pane review requests
** Keeping an eye on other pref pane patches and adding comments where appropriate
* KaiRo
** {{bug|437643}} is tracking the comm-central switch
** Worked on all kind of dependencies of this
** build system patches are up for review on {{bug|444686}}
** buildbot builders are ready to do comm-central builds, unix and Mac will have codesize data, we're losing Ts/Tp/Txul and graphs, would need talos machines for good perf data/stats
** discussed general L10n story on 1.9.1/hg, see {{bug|434289}}
** 1.1.11 is ready for release, contains security fixes to sync up with FF 3.0.1
** As always, [http://home.kairo.at/blog/ my blog] has more detailed status about my work
* mcsmurf
** {{bug|441050}} Continued to work on shell service UI, uploaded a patch, got review, working on a new patch
** Helped Serge to get some patches into the tree ;-)
* Mnyromyr
** Spent too much time debugging Growl integration. :-P
** Got some old reviews done, queue growing nonetheless - busy pref panel migrators! :-D
* Neil
* Ratty
** {{bug|428216}} (Toolbar button size/mode control): submitted the xul/xml/js part for review. Working on the CSS part.
** {{bug|425145}} (support for wallet.crypto.autocompleteoverride): after discussion in dev.apps.firefox, Justin Dokske pointed out that there are already observer hooks in nsLoginManager.js to which we can listen to and then fire off <tt>LoginManager._fillForm()</tt> with the ignoreAutocomplete parameter.
* Standard8
** Re-started work on {{bug|408613}} - migrating the "Addressing" preference pane, first step: split out edit directories dialog. Next step: move away the menus from rdf and unify with the Thunderbird code.
* stefanh

=== Any other business? ===

* Feeds
** Should we create additional CSS rule(s) to hide the Feed Discovery icon in URLBar for our alpha release so we don't confuse early testers who might expect Feed Subscribe/Preview to work when they see that? --[[User:Callek|Justin Wood (Callek)]] 19:55, 13 July 2008 (PDT)
** How about just adding <tt>hidden="true"</tt> to the XUL since this is just (presumably) temporary? --[[User:Philip Chee|Ratty]] 01:27, 14 July 2008 (PDT)
*** Sounds like a good enough solution, but "do we actually want it hidden"? --[[User:Callek|Justin Wood (Callek)]] 19:53, 14 July 2008 (PDT)

* Modern Theme (Help Wanted)
** From <tt>#seamonkey
*** [KaiRo] Ratty: looks like someone should ask the [https://addons.mozilla.org/en-US/firefox/user/4206 dev] of https://addons.mozilla.org/firefox/addon/7249 ([http://maguroban.s41.xrea.com/theme/pastmodern.html Past Modern]) to contribute stuff to SM2, we could need work on Modern ;-)
*** [Ratty] KaiRo: Actually that was what I was thinking of when I mentioned that Modern needed some work in the last meeting. I think the graphics come from the author of Phoenity (who is from the same country as I am actually)
*** [KaiRo] Ratty: yes, we really should get in touch with someone who cares about Modern - and this dev probably already has done the part we are missing completely atm (mozapps)
*** [KaiRo] RattyAway: could you try to contact those people?
*** [RattyAway] KaiRo: Sure.</tt>
** FYI:These people ususally hang out in the [http://forums.mozillazine.org/viewforum.php?f=18 Theme Development forum] in Mozillazine --[[User:Philip Chee|Ratty]] 11:51, 14 July 2008 (PDT)

SeaMonkey:StatusMeetings:2008-06-xx

2008-06-22T20:06:31Z

Ajschult: add Roundtable bits

[[SeaMonkey:StatusMeetings|index]]

'''SeaMonkey Meeting Details'''

* This is the first status report for the SeaMonkey project, no schedule for a discussion of this does exist yet.
* Information is dated June 2008 (Week 25)

== Agenda ==

=== Action Items ===

=== SeaMonkey 2 Alpha ===

[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a1%2B all blockers]
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0a1%3F blocker requests]

* {{bug|381157}} download manager
** Status?
* {{bug|390025}} kill-wallet (password manager)
** Status?
* {{bug|394522}} prefwindow move
** all top-level panes migrated
** Status of other panes?

=== Longer-Term SeaMonkey 2 Planning ===

* We might want to move to Gecko 1.9.1 with this release
* We now have a blocking-seamonkey2 flag on Bugs

=== Roundtable ===

Status Updates from developers - what are you working on, what's the progress, any other comments?

* ajschult
** QA for 1.1.10
** a couple outstanding reviews, including session store
* biesi
* Callek
* IanN
* KaiRo:
** figuring out our build story for 1.9.1/hg, coordination with Thunderbird on that (maybe also with calendar folks)
** Starting the 1.1.10 release process, will need a respin due to late changes for the platform
** also see [http://home.kairo.at/blog/ my blog] for details of what I'm doing
* mcsmurf
** Working on the shellservice UI
* Mnyromyr
* Neil
* Ratty
** Toolbar customization bug
*** Split into smaller patches/bugs to make it easier to review.
*** Some (semi) unrelated enhancements should be split off as well.
*** Recent discussion over IRC between KaiRo and gavin indicates that Neil's patch for the toolkit side of toolbar customization can move ahead. In this case we can probably avoid the need to fork the customizeToolbar.* code.
** Discussion in m.d.a.firefox on how to support wallet.crypto.autocompleteoverride once we move to toolkit's login manager.
* Standard8

SeaMonkey:Moving Profiles from mozilla.org to Mozilla

2007-09-15T05:11:13Z

Ajschult: Narrow down who is affected by this

== Change of Profile Location ==
The vendor ID of SeaMonkey trunk builds will be changed soon from '''mozilla.org''' to '''Mozilla''' (see {{bug|393620}}). This will affect the location of the profiles. In the future, SeaMonkey will search for the profiles in the following locations:

{|class="standard-table"
|+ '''Profile Locations'''
!Operating System !! New location !! Old location
|-
|Unix || '''~/.mozilla/seamonkey/<ProfileName>''' || ~/.mozilla.org/seamonkey/<ProfileName>
|-
|Windows || '''%APPDATA%\Mozilla\SeaMonkey\Profiles\<ProfileName>\''' || %APPDATA%\mozilla.org\SeaMonkey\Profiles\<ProfileName>\
|-
|Mac OS X || ~/Library/Mozilla/SeaMonkey/Profiles/<ProfileName>/ || ('''profile location will not be affected by the change!''')
|-
|OS/2 || '''%MOZILLA_HOME%\Mozilla\SeaMonkey\Profiles\<ProfileName>\''' || %MOZILLA_HOME%\mozilla.org\SeaMonkey\Profiles\<ProfileName>\
|-
|}

== Making the change ==
=== What to copy ===
This means that if you have used a suiterunner trunk build and then upgrade to a new one, the new trunk build will not see your profile. To avoid this, you need to copy the profile directory (or directories, for multiple profiles) from the old to the new location, '''before''' starting a nightly build that has the change. In addition, you need to copy the file <tt>profiles.ini</tt> that is located in the same directory as the different profiles.

=== Which files to edit ===
In order to use the copied profiles, you need to edit the following files in each of the profiles:
* prefs.js
* user.js (if present)
* extensions.ini
In these files, you need to adapt the paths to reflect the new location. Take care to only change those instances of <tt>mozilla.org</tt> in those files that are related to a path on the local system!

The file
* secmod.db
also contains the profile path, but it should not be necessary to edit this file. '''Note''': it might be destructive to edit this ''binary'' file in a normal editor!

=== Files to remove ===
You should also remove the files
* XUL.mfasl
* XPC.mfasl
* panacea.dat
* xpti.dat
* compreg.dat
from each profile directory. These files are caches that contain the profile path but are automatically rebuilt when restarting SeaMonkey, so nothing is lost.

== Automating the change ==
For Unix systems, there is a [http://www.mozilla.org/projects/seamonkey/pmigrate.sh shell script] to automatically copy the profiles from the old to the new location and edit and remove the above files. You need to call it from a terminal using
pmigrate.sh <ProfileName>
So this needs to be done once for each profile.

== Further notes ==
* If something doesn't work after this change, please describe the problem in the newsgroup <tt>mozilla.dev.apps.seamonkey</tt>.

* If you want to try this out before the actual change is available in nightly builds, change the line <code>Vendor=mozilla.org</code> in the file <tt>application.ini</tt> to <code>Vendor=Mozilla</code>.

* You should only remove the old profile location, if you are certain that you will never run an old nightly build again.

ReferencePlatforms/Test/Linux FC6 (Tinderbox)

2007-07-14T06:49:26Z

Ajschult: typos

This is a procedure used to create bl-bldlnx03, the Linux performance test machine for trunk.

== Install Fedora Core 6 from CDs ==

While installing, select a custom installation; the following categories were selected.

= Package Selection =

While installing, select a the '''GNOME Desktop''' and then select Custom package development; the following categories were selected:

* '''Desktop Environments'''
** Gnome Desktop Environment
* '''Applications'''
** Editors
** Text-based internet
*** Add lynx
* '''Development'''
** Development Tools
** Development Libraries
** X Software Development
** GNOME Software Development
** Legacy Software Development
* '''Servers'''
** Turn all off, except for "Printing Support"
* '''Base System'''
** Turn ''off'' '''Dialup Networking'''
** Turn ''on'' System Tools

== Some Sys-prepping ==

# for s in auditd avahi-daemon acpid bluetooth cpuspeed hplip hidd mcstrans pcscd ntpd cups cups-config-daemon mdmonitor openibd smartd pcmcia isdn atd gpm anacron autofs apmd kudzu yum-updatesd; do chkconfig $s off; done
# chkconfig httpd on
# service httpd start
# Copy over cltbld's ssh keys from another tinderbox
# Switch to runlevel 3 (disable gdm)
edit /etc/inittab, change "id:5:initdefault:" to "id:3:initdefault:"
# switch to runlevel 3 now
init 3
# Disable unneeded services by moving to /etc/cron.*.disabled/, leaving only logrotate and anacron:

mkdir /etc/cron.daily.disabled/ /etc/cron.weekly.disabled/
mv /etc/cron.daily/prelink /etc/cron.daily/makewhatis.cron \
/etc/cron.daily/tmpwatch /etc/cron.daily/0logwatch /etc/cron.daily/cups \
/etc/cron.daily/rpm /etc/cron.daily/mlocate.cron \
/etc/cron.daily/beagle-crawl-system /etc/cron.weekly.disabled/
mv /etc/cron.weekly/makewhatis.cron /etc/cron.weekly.disabled/

The only services left in /etc/cron.*/ should be:

/etc/cron.daily/0anacron
/etc/cron.daily/logrotate
/etc/cron.monthly/0anacron
/etc/cron.weekly/0anacron

Add the following lines to ~/.bash_profile

export CVS_RSH=ssh
export CVSROOT=cltbld@cvs.mozilla.org:/cvsroot
export TBOX_CLIENT_CVS_DIR="/builds/tinderbox/mozilla/tools"
export DISPLAY=:0

== Set up test environment ==

Install Tinderbox as usual.

<h2>FIXME - test-only-tinderbox mode causes tinderbox to not be able to check out the client.mk because it uses CVS incorrectly, and removed the "mozilla" directory which must exist or tinderbox will not work.
 
Checking out the "window open test" (below) makes sure that the "mozilla" directory always exists, and works around this problem.</h2>

For each build dir,
# link in startup test
cd /builds/tinderbox/${build_dir}/
ln -s ../mozilla/tools/performance/startup/startup-test.html .
# check out window open test
cd /builds/tinderbox/${build_dir}/Linux_2.6.18-1.2798.fc6_Depend
cvs co mozilla/xpfe/test

Get Tp2 from http://mxr.mozilla.org/mozilla/source/tools/performance/pageload/

Install Tp2 in /var/www/html/pageload

Get pageset from pageloadserver

Install pageset in /var/www/html/content

Use custom .xinitrc:
/usr/libexec/vino-server &
xhost +localhost
metacity

Allow remote connections via VNC:
gconftool-2 -s -t bool /desktop/gnome/remote_access/prompt_enabled false
gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled true

Start X and in screen:
screen
startx

== Dependencies ==

The following RPMs are installed:

a2ps-4.13b-57 
acl-2.2.39-1.1 
acpid-1.0.4-5 
alacarte-0.10.0-1.fc6 
alsa-lib-1.0.12-2.fc6 
alsa-lib-devel-1.0.12-2.fc6 
alsa-utils-1.0.12-3.fc6 
anacron-2.3-41.fc6 
antlr-2.7.6-4jpp.2 
apmd-3.2.2-5 
apr-1.2.7-10 
apr-util-1.2.7-3 
aspell-0.60.3-7.1 
aspell-en-6.0-2.1 
at-3.1.8-82.fc6 
atk-1.12.2-1.fc6 
atk-devel-1.12.2-1.fc6 
at-spi-1.7.11-2.fc6 
at-spi-devel-1.7.11-2.fc6 
attr-2.4.32-1.1 
audiofile-0.2.6-5 
audiofile-devel-0.2.6-5 
audit-libs-1.2.8-1.fc6 
audit-libs-python-1.2.8-1.fc6 
authconfig-5.3.10-1 
authconfig-gtk-5.3.10-1 
autoconf-2.59-12 
autofs-5.0.1-0.rc2.10 
automake14-1.4p6-13 
automake15-1.5-16 
automake16-1.6.3-8 
automake17-1.7.9-7 
automake-1.9.6-2.1 
avahi-0.6.11-6.fc6 
avahi-glib-0.6.11-6.fc6 
basesystem-8.0-5.1.1 
bash-3.1-16.1 
bc-1.06-21 
beagle-0.2.10-3.fc6 
beagle-evolution-0.2.10-3.fc6 
beagle-gui-0.2.10-3.fc6 
beecrypt-4.1.2-10.1.1 
bind-libs-9.3.2-41.fc6 
bind-utils-9.3.2-41.fc6 
binutils-2.17.50.0.3-6 
bison-2.3-2.1 
bitmap-fonts-0.3-5.1.1 
bitstream-vera-fonts-1.10-7 
bluez-libs-3.7-1 
bluez-pin-0.30-5 
bluez-utils-2.25-12 
boost-1.33.1-6.1 
boost-devel-1.33.1-6.1 
brlapi-0.4.1-1.fc6 
bug-buddy-2.16.0-1.fc6 
byacc-1.9-29.2.2 
bzip2-1.0.3-3 
bzip2-devel-1.0.3-3 
bzip2-libs-1.0.3-3 
cadaver-0.22.3-4 
cairo-1.2.4-1.fc6 
cairo-devel-1.2.4-1.fc6 
cairo-java-1.0.5-3.fc6 
ccid-1.0.1-5 
cdparanoia-libs-alpha9.8-27.2 
cdrdao-1.2.1-2 
cdrecord-2.01-10 
chkconfig-1.3.30-1 
chkfontpath-1.10.1-1.1 
compat-libstdc++-296-2.96-138 
compat-libstdc++-33-3.2.3-61 
compiz-0.0.13-0.32.20060817git.fc6 
comps-extras-11.1-1.1 
control-center-2.16.0-9.fc6 
coolkey-1.0.1-10 
coolkey-devel-1.0.1-10 
coreutils-5.97-11 
cpio-2.6-19 
cpp-4.1.1-30 
cpuspeed-1.2.1-1.40.fc6 
cracklib-2.8.9-3.1 
cracklib-dicts-2.8.9-3.1 
crash-4.0-3.3 
crontabs-1.10-8 
cryptsetup-luks-1.0.3-2.1 
cscope-15.5-15.fc6.1 
ctags-5.6-1.1 
cups-1.2.4-9 
cups-libs-1.2.4-9 
curl-7.15.5-1.fc6 
curl-devel-7.15.5-1.fc6 
cvs-1.11.22-4 
cyrus-sasl-2.1.22-4 
cyrus-sasl-devel-2.1.22-4 
cyrus-sasl-lib-2.1.22-4 
cyrus-sasl-plain-2.1.22-4 
db4-4.3.29-9.fc6 
db4-devel-4.3.29-9.fc6 
dbus-0.93-3.fc6 
dbus-devel-0.93-3.fc6 
dbus-glib-0.70-4 
dbus-glib-devel-0.70-4 
dbus-python-0.70-6 
dbus-x11-0.93-3.fc6 
dejavu-lgc-fonts-2.10-1 
desktop-backgrounds-basic-2.0-37 
desktop-file-utils-0.10-7 
desktop-printing-0.19-16.fc6 
devhelp-0.12-6.fc6 
device-mapper-1.02.07-3 
device-mapper-multipath-0.4.7-5 
dhcdbd-2.1-1.fc6 
dhclient-3.0.4-21.fc6 
dhcpv6_client-0.10-32.fc6 
diffstat-1.41-1.2.2 
diffutils-2.8.1-15.2.2 
diskdumputils-1.3.6-5.1 
dmidecode-2.7-1.26.1.fc6 
dmraid-1.0.0.rc13-1.fc6 
docbook-dtds-1.0-30.1 
docbook-style-dsssl-1.79-4.1 
docbook-style-xsl-1.69.1-5.1 
docbook-utils-0.6.14-5.1 
dos2unix-3.1-27.1 
dosfstools-2.11-6.1.fc6 
doxygen-1.4.7-1.1 
dump-0.4b41-2.fc6 
dvd+rw-tools-6.1-4.1 
e2fsprogs-1.39-7 
e2fsprogs-devel-1.39-7 
e2fsprogs-libs-1.39-7 
ed-0.2-38.2.2 
eel2-2.16.0-1.fc6 
eel2-devel-2.16.0-1.fc6 
eject-2.1.5-4 
elfutils-0.123-1.fc6 
elfutils-libelf-0.123-1.fc6 
elfutils-libelf-devel-0.123-1.fc6 
elfutils-libs-0.123-1.fc6 
elinks-0.11.1-5 
enscript-1.6.4-4.fc6 
eog-2.16.0.1-2.fc6 
esc-1.0.0-16.fc6 
esound-0.2.36-3 
esound-devel-0.2.36-3 
ethtool-3-1.2.2 
evince-0.6.0-3.fc6 
evolution-2.8.0-7.fc6 
evolution-data-server-1.8.0-11.fc6 
evolution-data-server-devel-1.8.0-11.fc6 
evolution-sharp-0.11.1-10.fc6 
expat-1.95.8-8.2.1 
expat-devel-1.95.8-8.2.1 
fbset-2.1-22 
fedora-logos-6.0.6-1.fc6 
fedora-release-6-4 
fedora-release-notes-6-3 
festival-1.95-5.2.1 
fetchmail-6.3.4-1.1 
file-4.17-8 
file-roller-2.16.0-2.fc6 
filesystem-2.4.0-1 
findutils-4.2.27-4.1 
finger-0.17-32.2.1.1 
firefox-1.5.0.7-7.fc6 
firefox-devel-1.5.0.7-7.fc6 
firstboot-1.4.23-1 
firstboot-tui-1.4.23-1 
flac-1.1.2-27 
flex-2.5.4a-41.fc6 
fontconfig-2.4.1-3.fc6 
fontconfig-devel-2.4.1-3.fc6 
foomatic-3.0.2-38 
freetype-2.2.1-10.fc6 
freetype-devel-2.2.1-10.fc6 
frysk-0.0.1.2006.10.02.rh1-1.fc6 
ftp-0.17-33.fc6 
gail-1.9.2-1.fc6 
gail-devel-1.9.2-1.fc6 
gamin-0.1.7-7.fc6 
gawk-3.1.5-11 
gcalctool-5.8.24-2.fc6 
gcc-4.1.1-30 
gcc-c++-4.1.1-30 
gcc-gfortran-4.1.1-30 
GConf2-2.14.0-2.1 
GConf2-devel-2.14.0-2.1 
gd-2.0.33-9.3.fc6 
gdb-6.5-8.fc6 
gdbm-1.8.0-26.2.1 
gdbm-devel-1.8.0-26.2.1 
gd-devel-2.0.33-9.3.fc6 
gdm-2.16.0-10.fc6 
gedit-2.15.9-1.fc6 
gettext-0.14.6-3.fc6 
ghostscript-8.15.2-8.1 
ghostscript-fonts-5.50-13.1.1 
giflib-4.1.3-7.1 
giflib-devel-4.1.3-7.1 
gimp-print-4.2.7-22 
gimp-print-utils-4.2.7-22 
gjdoc-0.7.7-11 
glade2-2.12.1-5.fc6 
glib2-2.12.3-2.fc6 
glib2-devel-2.12.3-2.fc6 
glibc-2.5-3 
glibc-common-2.5-3 
glibc-devel-2.5-3 
glibc-headers-2.5-3 
glib-java-0.2.6-3.fc6 
glx-utils-6.5.1-7.fc6 
gmime-2.2.3-3.fc6 
gmime-sharp-2.2.3-3.fc6 
gmp-4.1.4-7 
gmp-devel-4.1.4-7 
gnome-applets-2.16.0.1-7.fc6 
gnome-audio-2.0.0-3.1.1 
gnome-backgrounds-2.15.92-1.fc6 
gnome-bluetooth-0.7.0-10.1 
gnome-bluetooth-libs-0.7.0-10.1 
gnome-desktop-2.16.0-1.fc6 
gnome-desktop-devel-2.16.0-1.fc6 
gnome-doc-utils-0.8.0-2.fc6 
gnome-icon-theme-2.16.0.1-2.fc6 
gnome-keyring-0.6.0-1.fc6 
gnome-keyring-devel-0.6.0-1.fc6 
gnome-mag-0.13.1-1.fc6 
gnome-media-2.16.1-2.fc6 
gnome-menus-2.16.0-2.fc6 
gnome-mime-data-2.4.2-3.1 
gnome-mount-0.5-2.fc6 
gnome-netstatus-2.12.0-5.1 
gnome-panel-2.16.0-4.fc6 
gnome-panel-devel-2.16.0-4.fc6 
gnome-pilot-2.0.13-16 
gnome-pilot-devel-2.0.13-16 
gnome-power-manager-2.16.0-3.fc6 
gnome-python2-2.16.0-1.fc6 
gnome-python2-applet-2.16.0-1.fc6 
gnome-python2-bonobo-2.16.0-1.fc6 
gnome-python2-canvas-2.16.0-1.fc6 
gnome-python2-desktop-2.16.0-1.fc6 
gnome-python2-extras-2.14.2-4.fc6 
gnome-python2-gconf-2.16.0-1.fc6 
gnome-python2-gnomeprint-2.16.0-1.fc6 
gnome-python2-gnomevfs-2.16.0-1.fc6 
gnome-python2-gtksourceview-2.16.0-1.fc6 
gnome-python2-libegg-2.14.2-4.fc6 
gnome-screensaver-2.16.0-7.fc6 
gnome-session-2.16.0-3.fc6 
gnome-sharp-2.16.0-1.fc6 
gnome-speech-0.4.5-1.fc6 
gnome-spell-1.0.7-3.1 
gnome-system-monitor-2.16.0-1.fc6 
gnome-terminal-2.16.0-2.fc6 
gnome-themes-2.16.0-1.fc6 
gnome-user-docs-2.16.0-2.fc6 
gnome-user-share-0.10-5 
gnome-utils-2.16.0-1.fc6 
gnome-vfs2-2.16.0-4.fc6 
gnome-vfs2-devel-2.16.0-4.fc6 
gnome-vfs2-smb-2.16.0-4.fc6 
gnome-volume-manager-2.15.0-2.fc6 
gnupg-1.4.5-4 
gnutls-1.4.1-2 
gok-1.2.0-1.fc6 
gphoto2-2.2.0-2.1 
gpm-1.20.1-74.1 
gpm-devel-1.20.1-74.1 
grep-2.5.1-54.1 
groff-1.18.1.1-11.1 
grub-0.97-13 
gsf-sharp-0.8.1-2.fc6 
gstreamer-0.10.9-2 
gstreamer-plugins-base-0.10.9-4 
gstreamer-plugins-good-0.10.4-1.fc6 
gstreamer-tools-0.10.9-2 
gthumb-2.7.8-3.fc6 
gtk2-2.10.4-4.fc6 
gtk2-devel-2.10.4-4.fc6 
gtk2-engines-2.8.0-1.fc6 
gtk-doc-1.7-1.fc6 
gtkhtml3-3.12.0-1.fc6 
gtk-sharp2-2.10.0-3.fc6 
gtksourceview-1.8.0-1.fc6 
gtkspell-2.0.11-2.1 
gucharmap-1.8.0-1.fc6 
gzip-1.3.5-9 
hal-0.5.8.1-4.fc6 
hal-cups-utils-0.6.2-4 
hal-devel-0.5.8.1-4.fc6 
hdparm-6.6-2 
hesiod-3.1.0-8 
hesiod-devel-3.1.0-8 
hicolor-icon-theme-0.9-2.1 
hpijs-1.6.7-4 
hplip-1.6.7-4 
htmlview-3.0.0-14.1 
httpd-2.2.3-5 
hwdata-0.191-1 
ifd-egate-0.05-15 
imake-1.0.2-3 
im-chooser-0.3.3-2.fc6 
indent-2.2.9-14.fc6 
info-4.8-11.1 
initscripts-8.45.3-1 
iproute-2.6.16-6.fc6 
ipsec-tools-0.6.5-6 
iptables-1.3.5-1.2.1 
iptables-ipv6-1.3.5-1.2.1 
iptstate-1.4-1.1.2.2 
iputils-20020927-41.fc6 
irda-utils-0.9.17-2.fc6 
irqbalance-1.13-4.fc6 
java-1.4.2-gcj-compat-1.4.2.0-40jpp.110 
jpackage-utils-1.6.6-1jpp.8 
jwhois-3.2.3-6.1 
kbd-1.12-18 
kernel-2.6.18-1.2798.fc6 
kernel-devel-2.6.18-1.2798.fc6 
kernel-headers-2.6.18-1.2798.fc6 
kpartx-0.4.7-5 
krb5-auth-dialog-0.7-1 
krb5-devel-1.5-7 
krb5-libs-1.5-7 
krb5-workstation-1.5-7 
krbafs-1.2.2-10.1 
krbafs-devel-1.2.2-10.1 
ksh-20060214-1.1 
kudzu-1.2.57.1-2 
kudzu-devel-1.2.57.1-2 
lcms-1.15-1.2.2 
less-394-4.1 
lftp-3.5.1-2.fc6 
libacl-2.2.39-1.1 
libacl-devel-2.2.39-1.1 
libao-0.8.6-3 
libart_lgpl-2.3.17-4 
libart_lgpl-devel-2.3.17-4 
libattr-2.4.32-1.1 
libattr-devel-2.4.32-1.1 
libavc1394-0.5.3-1.fc6 
libbeagle-0.2.10-3.fc6 
libbonobo-2.16.0-1.fc6 
libbonobo-devel-2.16.0-1.fc6 
libbonoboui-2.16.0-1.fc6 
libbonoboui-devel-2.16.0-1.fc6 
libbtctl-0.6.0-9.1 
libcap-1.10-25 
libcap-devel-1.10-25 
libcroco-0.6.1-2.1 
libcroco-devel-0.6.1-2.1 
libdaemon-0.10-3.2 
libdmx-1.0.2-3.1 
libdrm-2.0.2-1.1 
libdrm-devel-2.0.2-1.1 
libdv-0.104-4.fc6.1 
libevent-1.1a-3.2.1 
libexif-0.6.13-2 
libfontenc-1.0.2-2.1 
libfontenc-devel-1.0.2-2.1 
libFS-1.0.0-3.1 
libgail-gnome-1.1.3-1.2.1 
libgcc-4.1.1-30 
libgcj-4.1.1-30 
libgconf-java-2.12.4-4.fc6 
libgcrypt-1.2.3-1 
libgcrypt-devel-1.2.3-1 
libgdiplus-1.1.17-1.fc6 
libgfortran-4.1.1-30 
libglade2-2.6.0-2 
libglade2-devel-2.6.0-2 
libglade-java-2.12.5-3.fc6 
libgnome-2.16.0-4.fc6 
libgnomecanvas-2.14.0-4.1 
libgnomecanvas-devel-2.14.0-4.1 
libgnomecups-0.2.2-8 
libgnome-devel-2.16.0-4.fc6 
libgnome-java-2.12.4-3.fc6 
libgnomeprint22-2.12.1-8 
libgnomeprint22-devel-2.12.1-8 
libgnomeprintui22-2.12.1-6 
libgnomeprintui22-devel-2.12.1-6 
libgnomeui-2.16.0-4.fc6 
libgnomeui-devel-2.16.0-4.fc6 
libgomp-4.1.1-30 
libgpg-error-1.4-2 
libgpg-error-devel-1.4-2 
libgsf-1.14.1-6 
libgsf-devel-1.14.1-6 
libgssapi-0.10-1 
libgtk-java-2.8.6-4.fc6 
libgtop2-2.14.4-2.fc6 
libgtop2-devel-2.14.4-2.fc6 
libICE-1.0.1-2.1 
libICE-devel-1.0.1-2.1 
libIDL-0.8.7-1.fc6 
libIDL-devel-0.8.7-1.fc6 
libidn-0.6.5-1.1 
libidn-devel-0.6.5-1.1 
libiec61883-1.0.0-11.fc6 
libieee1284-0.2.9-3.2.2 
libjpeg-6b-37 
libjpeg-devel-6b-37 
libmng-1.0.9-5.1 
libmng-devel-1.0.9-5.1 
libnl-1.0-0.10.pre5.4 
libnotify-0.4.2-4.fc6 
libogg-1.1.3-2.fc6 
libogg-devel-1.1.3-2.fc6 
liboil-0.3.8-2.1 
libpcap-0.9.4-8.1 
libpfm-3.2-0.060621.8.1 
libpng-1.2.10-7 
libpng-devel-1.2.10-7 
libraw1394-1.2.1-1.fc6 
librsvg2-2.16.0-2.fc6 
librsvg2-devel-2.16.0-2.fc6 
libsane-hpaio-1.6.7-4 
libselinux-1.30.29-2 
libselinux-devel-1.30.29-2 
libselinux-python-1.30.29-2 
libsemanage-1.6.17-1 
libsepol-1.12.27-1 
libsepol-devel-1.12.27-1 
libsilc-1.0.2-2.fc6 
libSM-1.0.1-3.1 
libSM-devel-1.0.1-3.1 
libsoup-2.2.96-4.fc6 
libstdc++-4.1.1-30 
libstdc++-devel-4.1.1-30 
libsysfs-2.0.0-6 
libtermcap-2.0.8-46.1 
libtermcap-devel-2.0.8-46.1 
libtheora-1.0alpha7-1 
libtiff-3.8.2-6.fc6 
libtiff-devel-3.8.2-6.fc6 
libtool-1.5.22-6.1 
libusb-0.1.12-5.1 
libuser-0.54.7-2 
libuser-devel-0.54.7-2 
libutempter-1.1.4-3.fc6 
libvolume_id-095-14 
libvorbis-1.1.2-1.2.1 
libvorbis-devel-1.1.2-1.2.1 
libvte-java-0.12.1-4.fc6 
libwnck-2.16.0-4.fc6 
libwvstreams-4.2.2-2.1 
libX11-1.0.3-4.fc6 
libX11-devel-1.0.3-4.fc6 
libXau-1.0.1-3.1 
libXau-devel-1.0.1-3.1 
libXaw-1.0.2-8.1 
libXaw-devel-1.0.2-8.1 
libXcomposite-0.3-5.1 
libXcomposite-devel-0.3-5.1 
libXcursor-1.1.7-1.1 
libXcursor-devel-1.1.7-1.1 
libXdamage-1.0.3-2.1 
libXdamage-devel-1.0.3-2.1 
libXdmcp-1.0.1-2.1 
libXdmcp-devel-1.0.1-2.1 
libXevie-1.0.1-3.1 
libXevie-devel-1.0.1-3.1 
libXext-1.0.1-2.1 
libXext-devel-1.0.1-2.1 
libXfixes-4.0.1-2.1 
libXfixes-devel-4.0.1-2.1 
libXfont-1.2.2-1.fc6 
libXfontcache-1.0.2-3.1 
libXfontcache-devel-1.0.2-3.1 
libXfont-devel-1.2.2-1.fc6 
libXft-2.1.10-1.1 
libXft-devel-2.1.10-1.1 
libXi-1.0.1-3.1 
libXi-devel-1.0.1-3.1 
libXinerama-1.0.1-2.1 
libXinerama-devel-1.0.1-2.1 
libxkbfile-1.0.3-3.1 
libxklavier-3.0-1.fc6 
libxml2-2.6.26-2.1.1 
libxml2-devel-2.6.26-2.1.1 
libxml2-python-2.6.26-2.1.1 
libXmu-1.0.2-5 
libXmu-devel-1.0.2-5 
libXpm-3.5.5-3 
libXpm-devel-3.5.5-3 
libXrandr-1.1.1-3.1 
libXrandr-devel-1.1.1-3.1 
libXrender-0.9.1-3.1 
libXrender-devel-0.9.1-3.1 
libXres-1.0.1-3.1 
libXres-devel-1.0.1-3.1 
libXScrnSaver-1.1.0-3.1 
libXScrnSaver-devel-1.1.0-3.1 
libxslt-1.1.17-1.1 
libxslt-devel-1.1.17-1.1 
libXt-1.0.2-3.1.fc6 
libXt-devel-1.0.2-3.1.fc6 
libXTrap-1.0.0-3.1 
libXTrap-devel-1.0.0-3.1 
libXtst-1.0.1-3.1 
libXtst-devel-1.0.1-3.1 
libXv-1.0.1-4.1 
libXv-devel-1.0.1-4.1 
libXvMC-1.0.2-2.1 
libXvMC-devel-1.0.2-2.1 
libXxf86dga-1.0.1-3.1 
libXxf86dga-devel-1.0.1-3.1 
libXxf86misc-1.0.1-3.1 
libXxf86misc-devel-1.0.1-3.1 
libXxf86vm-1.0.1-3.1 
libXxf86vm-devel-1.0.1-3.1 
linuxwacom-0.7.4_1-2.1 
lockdev-1.0.1-10 
lockdev-devel-1.0.1-10 
logrotate-3.7.4-7 
logwatch-7.3-5 
lsof-4.78-3 
ltrace-0.5-6.45svn.fc6 
lvm2-2.02.06-4 
lynx-2.8.5-28.1 
m4-1.4.5-3 
mailcap-2.1.23-1.fc6 
mailx-8.1.1-44.2.2 
make-3.81-1.1 
MAKEDEV-3.23-1.2 
man-1.6d-1.1 
man-pages-2.39-5 
mcstrans-0.1.8-3 
mdadm-2.5.4-2.fc6 
mesa-libGL-6.5.1-7.fc6 
mesa-libGL-devel-6.5.1-7.fc6 
mesa-libGLU-6.5.1-7.fc6 
mesa-libGLU-devel-6.5.1-7.fc6 
metacity-2.16.0-5.fc6 
mgetty-1.1.33-9.fc6 
microcode_ctl-1.13-1.33.fc6 
mingetty-1.07-5.2.2 
mkbootdisk-1.5.3-2.1 
mkinitrd-5.1.19-1 
mkisofs-2.01-10 
mktemp-1.5-23.2.2 
mlocate-0.14-2.1 
module-init-tools-3.3-0.pre1.4.17 
mono-core-1.1.17.1-3.fc6 
mono-data-1.1.17.1-3.fc6 
mono-data-sqlite-1.1.17.1-3.fc6 
mono-web-1.1.17.1-3.fc6 
mtools-3.9.10-2.fc6 
mtr-0.71-3.1 
mutt-1.4.2.2-2 
nano-1.3.12-1.1 
nash-5.1.19-1 
nautilus-2.16.0-5.fc6 
nautilus-cd-burner-2.16.0-3.fc6 
nautilus-extensions-2.16.0-5.fc6 
nautilus-sendto-0.7-5.fc6 
nautilus-sendto-bluetooth-0.7-5.fc6 
nc-1.84-10.fc6 
ncurses-5.5-24.20060715 
ncurses-devel-5.5-24.20060715 
neon-0.25.5-5.1 
neon-devel-0.25.5-5.1 
netdump-0.7.16-5 
netpbm-10.35-6.fc6 
netpbm-devel-10.35-6.fc6 
net-snmp-libs-5.3.1-11.fc6 
net-tools-1.60-73 
NetworkManager-0.6.4-5.fc6 
NetworkManager-glib-0.6.4-5.fc6 
NetworkManager-gnome-0.6.4-5.fc6 
newt-0.52.2-9 
newt-devel-0.52.2-9 
nfs-utils-1.0.9-8.fc6 
nfs-utils-lib-1.0.8-7.2 
nmap-4.11-1.1 
notification-daemon-0.3.5-6 
notify-python-0.1.0-3.fc6 
nscd-2.5-3 
nspr-4.6.3-1 
nspr-devel-4.6.3-1 
nss-3.11.3-2 
nss_db-2.2-35.1 
nss-devel-3.11.3-2 
nss_ldap-253-1 
nss-tools-3.11.3-2 
ntp-4.2.2p1-3 
ntsysv-1.3.30-1 
numactl-0.9.8-1.35 
opal-2.2.2-1.1 
openjade-1.3.2-27 
openldap-2.3.27-4 
openldap-clients-2.3.27-4 
openldap-devel-2.3.27-4 
openobex-1.3-3.1 
opensp-1.5.2-3.1 
openssh-4.3p2-10 
openssh-askpass-4.3p2-10 
openssh-clients-4.3p2-10 
openssh-server-4.3p2-10 
openssl-0.9.8b-8 
openssl-devel-0.9.8b-8 
oprofile-0.9.1-16 
oprofile-gui-0.9.1-16 
ORBit2-2.14.3-3.fc6 
ORBit2-devel-2.14.3-3.fc6 
orca-1.0.0-4.fc6 
pam-0.99.6.2-3.fc6 
pam_ccreds-3-5 
pam-devel-0.99.6.2-3.fc6 
pam_krb5-2.2.11-1 
pam_passwdqc-1.0.2-1.2.2 
pam_pkcs11-0.5.3-22 
pam_smb-1.1.7-7.2.1 
pango-1.14.4-3.fc6 
pango-devel-1.14.4-3.fc6 
paps-0.6.6-16.fc6 
parted-1.7.1-16.fc6 
passwd-0.73-1 
patch-2.5.4-29.2.2 
patchutils-0.2.31-2.2.2 
pax-3.4-1.2.2 
pciutils-2.2.3-4 
pciutils-devel-2.2.3-4 
pcmciautils-014-5 
pcre-6.6-1.1 
pcsc-lite-1.3.1-7 
pcsc-lite-devel-1.3.1-7 
pcsc-lite-libs-1.3.1-7 
perl-5.8.8-10 
perl-Archive-Tar-1.30-1.fc6 
perl-Compress-Zlib-1.42-1.fc6 
perl-Digest-HMAC-1.01-15 
perl-Digest-SHA1-2.11-1.2.1 
perl-HTML-Parser-3.55-1.fc6 
perl-HTML-Tagset-3.10-2.1.1 
perl-IO-Socket-INET6-2.51-2.fc6 
perl-IO-Socket-SSL-1.01-1.fc6 
perl-IO-Zlib-1.04-4.2.1 
perl-Net-DNS-0.59-1.fc6 
perl-Net-IP-1.25-2.fc6 
perl-Net-SSLeay-1.30-4.fc6 
perl-SGMLSpm-1.03ii-16.2.1 
perl-Socket6-0.19-3.fc6 
perl-String-CRC32-1.4-2.fc6 
perl-URI-1.35-3 
pfmon-3.2-0.060621.7.1 
pilot-link-0.11.8-16 
pilot-link-devel-0.11.8-16 
pinfo-0.6.9-1.fc6 
pirut-1.2.5-1 
pkgconfig-0.21-1.fc6 
pm-utils-0.19-3 
policycoreutils-1.30.30-1 
poppler-0.5.4-2.fc6 
poppler-utils-0.5.4-2.fc6 
popt-1.10.2-32 
portmap-4.0-65.2.2.1 
postgresql-libs-8.1.4-1.1 
ppp-2.4.4-1 
prelink-0.3.9-2 
procmail-3.22-17.1 
procps-3.2.7-8 
psacct-6.3.2-41.1 
psmisc-22.2-5 
pstack-1.2-7.2.2 
psutils-1.17-26.1 
pwlib-1.10.1-6.fc6 
pycairo-1.2.0-1.1 
pycairo-devel-1.2.0-1.1 
pygobject2-2.12.1-1.fc6 
pygobject2-devel-2.12.1-1.fc6 
pygtk2-2.10.1-4.fc6 
pygtk2-devel-2.10.1-4.fc6 
pygtk2-libglade-2.10.1-4.fc6 
pyorbit-2.14.1-1.1 
PyQt-3.16-4 
python-2.4.3-18.fc6 
python-devel-2.4.3-18.fc6 
python-elementtree-1.2.6-5 
python-ldap-2.2.0-2.1 
python-numeric-23.7-2.2.2 
python-sqlite-1.1.7-1.2.1 
python-urlgrabber-2.9.9-2 
pyxf86config-0.3.31-2.fc6 
PyXML-0.8.4-4 
qt-3.3.6-13 
quota-3.13-1.2.3.1 
rcs-5.7-30.1 
rdate-1.4-6 
rdist-6.1.5-44 
readahead-1.3-5 
readline-5.1-1.1 
readline-devel-5.1-1.1 
redhat-artwork-5.0.8-1.fc6 
redhat-lsb-3.1-11 
redhat-menus-6.7.5-3 
redhat-rpm-config-8.0.45-6 
rhgb-0.16.4-1.fc6 
rhpl-0.194-1 
rhpxl-0.39-2 
rmt-0.4b41-2.fc6 
rng-utils-2.0-1.14.1.fc6 
rootfiles-8.1-1.1.1 
rpm-4.4.2-32 
rpm-build-4.4.2-32 
rpm-devel-4.4.2-32 
rpm-libs-4.4.2-32 
rpm-python-4.4.2-32 
rp-pppoe-3.5-32.1 
rsh-0.17-36 
rsync-2.6.8-3.1 
samba-client-3.0.23c-2 
samba-common-3.0.23c-2 
sane-backends-1.0.18-5.fc6 
sane-backends-libs-1.0.18-5.fc6 
screen-4.0.2-15.1 
scrollkeeper-0.3.14-8.fc6 
SDL-1.2.10-6.2 
SDL-devel-1.2.10-6.2 
sed-4.1.5-5.fc6 
selinux-policy-2.3.18-10 
selinux-policy-targeted-2.3.18-10 
sendmail-8.13.8-2 
setarch-2.0-1.1 
setserial-2.17-19.2.2 
setup-2.5.55-1 
setuptool-1.18.1-1.2.1 
sgml-common-0.6.3-18 
shadow-utils-4.0.17-5 
shared-mime-info-0.19-1 
sip-4.4.5-3 
slang-2.0.6-3 
slang-devel-2.0.6-3 
slrn-0.9.8.1pl1-1.2.2 
smartmontools-5.36-3 
sox-12.18.1-1 
spamassassin-3.1.4-1.fc6 
specspo-12-1 
speex-1.0.5-2.1 
sqlite-3.3.6-2 
sqlite-devel-3.3.6-2 
startup-notification-0.8-4.1 
startup-notification-devel-0.8-4.1 
strace-4.5.14-3 
stunnel-4.15-2 
subversion-1.3.2-6 
sudo-1.6.8p12-10 
swig-1.3.29-1.fc6 
symlinks-1.2-24.2.2 
synaptics-0.14.4-8.fc6 
sysklogd-1.4.1-39.2 
syslinux-3.11-4 
sysreport-1.4.3-9 
system-config-date-1.8.7-1 
system-config-display-1.0.45-1 
system-config-keyboard-1.2.10-2 
system-config-language-1.1.11-2 
system-config-lvm-1.0.18-1.2.FC6 
system-config-network-1.3.95-1 
system-config-network-tui-1.3.95-1 
system-config-printer-0.7.32-1 
system-config-printer-libs-0.7.32-1 
system-config-rootpassword-1.1.9-1 
system-config-securitylevel-1.6.27-1 
system-config-securitylevel-tui-1.6.27-1 
system-config-services-0.9.1-1.fc6 
system-config-soundcard-2.0.3-2.fc6 
system-config-users-1.2.46-1.fc6 
systemtap-0.5.9-1.fc6 
SysVinit-2.86-14 
talk-0.17-29.2.2 
tar-1.15.1-19 
tcpdump-3.9.4-8.1 
tcp_wrappers-7.6-40.2.1 
tcsh-6.14-11 
telnet-0.17-37 
termcap-5.5-1.20060701.1 
texinfo-4.8-11.1 
time-1.7-27.2.2 
tmpwatch-2.9.7-1.1 
tomboy-0.4.1-1.fc6 
traceroute-1.0.4-2 
tree-1.5.0-4 
ttmkfdir-3.0.9-22 
tzdata-2006m-2.fc6 
udev-095-14 
unix2dos-2.2-26.2.2 
unzip-5.52-2.2.1 
urw-fonts-2.3-6.1.1 
usbutils-0.71-2.1 
usermode-1.87-3 
usermode-gtk-1.87-3 
util-linux-2.13-0.44.fc6 
valgrind-3.2.1-4 
vconfig-1.9-2.1 
vim-common-7.0.109-3 
vim-enhanced-7.0.109-3 
vim-minimal-7.0.109-3 
vino-2.13.5-4.1 
vixie-cron-4.1-64.fc6 
vnc-4.1.2-3.fc6 
vnc-server-4.1.2-3.fc6 
vte-0.14.0-1.fc6 
wget-1.10.2-7 
which-2.16-7 
wireless-tools-28-1.fc6 
words-3.0-9 
wpa_supplicant-0.4.8-10.1.fc6 
Xaw3d-1.5E-10.1 
Xaw3d-devel-1.5E-10.1 
xdelta-1.1.3-20 
xkeyboard-config-0.8-7.fc6 
xml-common-0.6.3-18 
xorg-x11-apps-7.1-3.fc6 
xorg-x11-docs-1.2-4.fc6 
xorg-x11-drivers-7.1-3 
xorg-x11-drv-acecad-1.1.0-2.1 
xorg-x11-drv-aiptek-1.0.1-2 
xorg-x11-drv-apm-1.1.1-2.1 
xorg-x11-drv-ark-0.6.0-2.1 
xorg-x11-drv-ast-0.81.0-3 
xorg-x11-drv-ati-6.6.2-4.fc6 
xorg-x11-drv-calcomp-1.1.0-1.1 
xorg-x11-drv-chips-1.1.1-2.1 
xorg-x11-drv-cirrus-1.1.0-2.fc6 
xorg-x11-drv-citron-2.2.0-1.1 
xorg-x11-drv-cyrix-1.1.0-4 
xorg-x11-drv-digitaledge-1.1.0-1.1 
xorg-x11-drv-dmc-1.1.0-2 
xorg-x11-drv-dummy-0.2.0-2.1 
xorg-x11-drv-dynapro-1.1.0-2 
xorg-x11-drv-elo2300-1.1.0-1.1 
xorg-x11-drv-elographics-1.1.0-1.1 
xorg-x11-drv-evdev-1.1.2-2.1 
xorg-x11-drv-fbdev-0.3.0-2 
xorg-x11-drv-fpit-1.1.0-1.1 
xorg-x11-drv-glint-1.1.1-4.1 
xorg-x11-drv-hyperpen-1.1.0-2 
xorg-x11-drv-i128-1.2.0-4 
xorg-x11-drv-i740-1.1.0-2.1 
xorg-x11-drv-i810-1.6.5-9.fc6 
xorg-x11-drv-jamstudio-1.1.0-1.1 
xorg-x11-drv-joystick-1.1.0-1.1 
xorg-x11-drv-keyboard-1.1.0-2.1 
xorg-x11-drv-magellan-1.1.0-1.1 
xorg-x11-drv-magictouch-1.0.0.5-2.1 
xorg-x11-drv-mga-1.4.2-1.fc6 
xorg-x11-drv-microtouch-1.1.0-1.1 
xorg-x11-drv-mouse-1.1.1-1.1 
xorg-x11-drv-mutouch-1.1.0-2 
xorg-x11-drv-neomagic-1.1.1-2.1 
xorg-x11-drv-nsc-2.8.1-2.1 
xorg-x11-drv-nv-1.2.0-4.fc6 
xorg-x11-drv-palmax-1.1.0-1.1 
xorg-x11-drv-penmount-1.1.0-2.1 
xorg-x11-drv-rendition-4.1.0-3.1 
xorg-x11-drv-s3-0.4.1-2.1 
xorg-x11-drv-s3virge-1.9.1-2.1 
xorg-x11-drv-savage-2.1.1-5.fc6 
xorg-x11-drv-siliconmotion-1.4.1-2.1 
xorg-x11-drv-sis-0.9.1-7 
xorg-x11-drv-sisusb-0.8.1-4.1 
xorg-x11-drv-spaceorb-1.1.0-1.1 
xorg-x11-drv-summa-1.1.0-1.1 
xorg-x11-drv-tdfx-1.2.1-3.1 
xorg-x11-drv-trident-1.2.1-3.fc6 
xorg-x11-drv-tseng-1.1.0-3.1 
xorg-x11-drv-ur98-1.1.0-1.1 
xorg-x11-drv-v4l-0.1.1-4 
xorg-x11-drv-vesa-1.2.1-4 
xorg-x11-drv-vga-4.1.0-2.1 
xorg-x11-drv-via-0.2.1-7 
xorg-x11-drv-vmmouse-12.4.0-2.1 
xorg-x11-drv-vmware-10.13.0-2.1 
xorg-x11-drv-void-1.1.0-3.1 
xorg-x11-drv-voodoo-1.1.0-3.1 
xorg-x11-filesystem-7.1-2.fc6 
xorg-x11-fonts-100dpi-7.1-2 
xorg-x11-fonts-75dpi-7.1-2 
xorg-x11-fonts-base-7.1-2 
xorg-x11-fonts-ISO8859-1-100dpi-7.1-2 
xorg-x11-fonts-ISO8859-1-75dpi-7.1-2 
xorg-x11-fonts-misc-7.1-2 
xorg-x11-fonts-truetype-7.1-2 
xorg-x11-fonts-Type1-7.1-2 
xorg-x11-font-utils-7.1-2 
xorg-x11-proto-devel-7.1-9.fc6 
xorg-x11-server-utils-7.1-4.fc6 
xorg-x11-server-Xorg-1.1.1-47.fc6 
xorg-x11-twm-1.0.1-3.1 
xorg-x11-util-macros-1.0.2-4.fc6 
xorg-x11-utils-7.1-2.fc6 
xorg-x11-xauth-1.0.1-2.1 
xorg-x11-xfs-1.0.2-3.1 
xorg-x11-xinit-1.0.2-12.fc6 
xorg-x11-xkb-utils-1.0.2-2.1 
xorg-x11-xtrans-devel-1.0.1-1.1.fc6 
xrestop-0.2-6.2.2 
xsri-2.1.0-10.fc6 
xterm-215-3.fc6 
yelp-2.16.0-4.fc6 
ypbind-1.19-5 
yp-tools-2.9-0.1 
yum-3.0-6 
yum-metadata-parser-1.0-8.fc6 
yum-updatesd-3.0-6 
zenity-2.16.0-1.fc6 
zip-2.31-1.2.2 
zisofs-tools-1.0.6-3.2.2 
zlib-1.2.3-3 
zlib-devel-1.2.3-3 
zsh-4.2.6-1

Talk:Linux/Runtime Requirements

2007-06-29T04:08:21Z

Ajschult: Buildtime/Runtime

So basically this is saying that to be a Mozilla developer or tester you must have Fedora Core 6 or later (or equivalent for other distros) installed, right?

Has someone considered doing a survey of how many current developers and testers will be affected by that requirement? I'm guessing not all that many in the end, but it would be good to have some hard numbers.

Fedora Core 6 meets the requirements except for cairo 1.4 (it has 1.2.6). Does listing cairo here as a runtime requirement mean that that using system cairo would be the default build option?

Please do not impose GNOME as a requirement - the Gtk/Pango/Cairo
dependencies are manageable, but GNOME is a beast that many of us would rather
avoid (and stick to KDE/Xfce). Thanks.

Could we actually get a list of the major distributions/versions that would meet the requirements specified here? They seem a little high. --[[User:Standard8|Standard8]] 08:33, 18 May 2007 (PDT)

Sigh. Can we stop completely saying "Runtime" when "Buildtime" is meant? The -devel packages are *totally* not runtime requirements. If build time requirements need to be listed, that's fine but they should be on a page related to build time requirements and this is not that page! It's also be nice if this weren't an entirely one-sided discussion, but I guess I shouldn't have expected more from a wiki. --[[User:Ajschult|Ajschult]]

= Specific distros =
== Debian ==

Is this going to cut Debian 4.0 "Etch" off in the next half a year? The libraries in question are (though they might contain a mix of newer versions in them...):

*libgtk2.0-0 2.8.20-7
*GNOME is a mix of 2.14 and 2.16 packages, but libgnome2-0 is 2.16
*libcairo2 1.2.4-4

...and Minefield still works on Sarge (3.1), except that its logo is not rendered.

== What about Sun and BSD? ==

Will these requirements apply to Sun and BSD? Or any platform using Gtk2, for that matter?

Talk:Linux/Runtime Requirements

2007-05-12T21:52:32Z

Ajschult:

SeaMonkey:Scratchpad:Migration Announcement

2007-03-09T15:34:41Z

Ajschult: typo fix

The SeaMonkey team wants to get the word out publicly 1) that Mozilla suite users should upgrade and 2) that the SeaMonkey project exists and what it is.

We want to get this out to the press in all regions where we have our software available in local languages, which means that we're 1) asking our SeaMonkey L10n teams to localize this announcement and 2) asking peers in all local communities to send this out to the local press.

== Original (English, US) version ==

=== SeaMonkey project urges Mozilla users to upgrade ===

Two years after the end-of-line announcement for the Mozilla Application suite, 10 months after its last security update and more than a year after the first release of its successor, the SeaMonkey team tries to win over people who are still using this Internet suite software.

"The Mozilla suite is outdated and insecure nowadays", tells Robert Kaiser of the project-leading SeaMonkey Council, "In the recent months, the list of known security vulnerabilities grew, but development has stopped on that Mozilla-branded suite. There is a successor with the same browser/mail/composer/chat combination, improved functionality, and a steady flow of security updates - just under a different name: SeaMonkey."

The name change was needed to officially show that a group of dedicated volunteers took over suite development in March 2005 from Mozilla Foundation, which focuses on development of the stand-alone Firefox browser and Thunderbird mail clients, which it also promotes as supported upgrade paths for users of the old Mozilla suite.

"We offer those users to stay the more familiar suite style with SeaMonkey instead of switching to differently working stand-alone applications", says Robert Kaiser, pointing to www.seamonkey-project.org for detailed information and downloads. "Security is very important on the Internet, so you should use software that gets updated for security problem regularly. Additionally, choice and innovation are goals of the Mozilla community, and as members of that community, we offer all that to Mozilla users through the SeaMonkey project."

SeaMonkey is an Open-Source community project within the mozilla.org software family.

SeaMonkey:Home Page

2006-08-06T22:35:37Z

Ajschult: add link to newsgroup

{{SeaMonkey-Resources}}

This Mozilla Wiki section covers documents about the '''[http://www.mozilla.org/projects/seamonkey/ 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|SeaMonkey FAQ]]!

== Status ==

The SeaMonkey project released [http://www.mozilla.org/projects/seamonkey/releases/ SeaMonkey 1.0] in January 2006, 1.0.1 in April 2006, 1.0.2 in June 2006 and 1.0.3 in July 2006 and will now continue development of that internet application suite in three ways:
*Firstly, 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").
*Secondly, 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 this work will be released as SeaMonkey 1.1, which will look and feel the same as 1.0 except for the newly added features. (This is done on the "Mozilla 1.8 branch".)
*Finally, we are working on migrating the entire application to the new backend framework used by our close relatives Firefox, Thunderbird, etc., and are even moving toward using the new [[XULRunner]] architecture. At the same time we're looking to restructure the SeaMonkey-specific code, aiming to have this code live in a more sensible structure in one common location. This work will mean less development differences between Firefox, Thunderbird and SeaMonkey, and will result in lots of new possibilites, such as having the new Extension Manager, a better localization framework ("source L10n") and a theme rework, but it will also mean some bigger changes in how SeaMonkey's backend behaves. Despite this, we'll try to retain the feel of the well-known suite as much as possible. The current working title for a release from that work is "SeaMonkey 1.5" (subject to change) with a release not to be expected before 2007. (This work is happening on "Mozilla trunk".)

([[Global:1.9 Trunk 1.8 Branch Plan]] explains the trunk and branches.)

== History ==

In 2005, the Mozilla Foundation released a [http://www.mozilla.org/seamonkey-transition.html "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.

== The team ==

A group of very active SeaMonkey developers make up the [[SeaMonkey:Project_Organization#SeaMonkey_Council|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 [[SeaMonkey:QA|people doing QA and regular testing]] on our product. The development community of SeaMonkey is structured into [http://www.mozilla.org/projects/seamonkey/project-areas.html 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 [mailto:seamonkey-council@mozilla.org seamonkey-council@mozilla.org].

Here is a page with a [[SeaMonkey:Supporters|list of the currently known supporters]].

== How to help ==

Our [[SeaMonkey:Project Goals|Project Goals]] document describes where the project is basically headed.

You can help by working on [[SeaMonkey:QA|SeaMonkey QA]] as you use SeaMonkey. We need help testing changes for SeaMonkey 1.0.x, SeaMonkey 1.1, and SeaMonkey 1.5.

To get started with the project, join in the developer discussions in or [news://news.mozilla.org/mozilla.dev.apps.seamonkey mozilla.dev.apps.seamonkey] or [irc://irc.mozilla.org/seamonkey #seamonkey].

== 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=255807 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.

The [[SeaMonkey:New for 1.5]] document details the new features we should be picking up for 1.5, these are mainly as a result of the toolkit 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.

[[category:SeaMonkey|*]]

SeaMonkey:Home Page

2006-03-02T19:05:02Z

Ajschult:

{{SeaMonkey-Resources}}

This Mozilla Wiki section covers documents about the '''[http://www.mozilla.org/projects/seamonkey/ 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|SeaMonkey FAQ]]!

== Status ==

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")
*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 as 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 [http://www.mozilla.org/seamonkey-transition.html "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:Project_Organization#SeaMonkey_Council|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 [[http://wiki.mozilla.org/SeaMonkey:QA|people doing QA and regular testing]] on our product. The development community of SeaMonkey is structured into [http://www.mozilla.org/projects/seamonkey/project-areas.html 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 [mailto:seamonkey-council@mozilla.org seamonkey-council@mozilla.org].

Here is a page with a [[SeaMonkey:Supporters|list of the currently known supporters]].

== How to help ==

Our [[SeaMonkey:Project Goals|Project Goals]] document describes where the project is basically headed.

You can help by working on [[SeaMonkey:QA|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 [https://bugzilla.mozilla.org/query.cgi?product=Mozilla%20Application%20Suite&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=blocking-seamonkey1.0.1 create your own query] with this flag, or view the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0.1%2B open approved bugs] and [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0.1%3F 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 [https://bugzilla.mozilla.org/query.cgi?product=Mozilla%20Application%20Suite&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=blocking-seamonkey1.1a create your own query] with this flag, or view the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.1a%2B open approved bugs] and [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.1a%3F 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=255807 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://irc.mozilla.org/seamonkey IRC] on '''Wednesday July 6th 2005 at 15:00 UTC''' ([http://www.hg23.at/~robert/thebot-logs/%23seamonkey-20050707-110024.xml log]).

If you have agenda items, please e-mail [mailto:ajvincent@gmail.com Alex Vincent] with your ideas.

SeaMonkey/QA

2006-02-03T05:39:59Z

Ajschult: mention bugzilla products

{{SeaMonkey-Resources}}

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page. At this point, we are particularly interested in getting smoketesters.

== SeaMonkey QA Call to Action ==

As we approach the release of [[SeaMonkey:First_Release|SeaMonkey 1.0]], we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

In preparation for the release of SeaMonkey 1.0, we need as many testers as possible to download and use [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8.0/ recent nightly Gecko 1.8.0 branch builds]. Testers who wish to test the changes for SeaMonkey 1.1 should download and use [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/ recent nightly Gecko 1.8 branch builds]. Testers who wish to test all the latest changes in preparation for the next major release of SeaMonkey (version 1.5) should download and use [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ recent nightly trunk builds]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. (Note: Talkback is currently working only for trunk builds.) If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug] in the "Mozilla Application Suite" or "Core" Products (see below). We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7, and bugs in recent trunk builds that do not exist in SeaMonkey 1.0), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&version=1.8+Branch&bug_status=UNCONFIRMED&chfieldfrom=2004-04-01&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&version=1.8+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, we'll be able to see what bugs need to be fixed before SeaMonkey 1.0, and what issues need to be reported in the release notes.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* '''Smoketests''' should be run regularly using [[SeaMonkey:QA:Testrunner|testrunner]] to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity. If you run the smoketests regularly, please add your name to the [[SeaMonkey:QA_Areas|QA Areas]] page. Please stop by [irc://moznet/seamonkey #seamonkey] for more about using testrunner.

* Work on an area identified by a developer as needing special attention, as identified on the [[SeaMonkey:QA_Wanted|QA Wanted]] page.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

* If you find a bug that you believe must be fixed before the next milestone (1.0a), nominate the bug to block release by setting the "blocking-seamonkey1.0a" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B bugs] the Council has already decided should block the next milestone.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] and [irc://irc.mozilla.org/bugs #bugs] generally have a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

* The [http://weblogs.mozillazine.org/seamonkey-qa/ SeaMonkey QA blog] will contain announcements of any changes in SeaMonkey QA needs.

SeaMonkey:First Release

2006-01-31T06:18:50Z

Ajschult: add a bit about XPrint

{{SeaMonkey-Resources}}

== SeaMonkey 1.0 release plan ==

SeaMonkey 1.0, the first release of our new project, will be what a "Mozilla 1.8" application suite was meant to be. As such, it will be released from the Gecko 1.8 base, which it will share with the Mozilla Firefox 1.5 and Thunderbird 1.5 releases.

The current plan is to release an Alpha and a Beta release from the Mozilla 1.8 branch on the way to that 1.0 release:
* [http://www.mozilla.org/projects/seamonkey/releases/1.0a.html SeaMonkey 1.0 Alpha] was released from Gecko 1.8b4, paralleling the Firefox and Thunderbird 1.5 Beta1 releases done by Mozilla Foundation. While the basic codebase may be more beta than alpha quality, our new release process is not completely settled, we don't have our final [http://www.mozilla.org/projects/seamonkey/artwork.html Artwork] yet and we have no dedicated release machines in place, so it's better to call this an early testing release or "Alpha".
* [http://www.mozilla.org/projects/seamonkey/releases/#1.0b SeaMonkey 1.0 Beta] was released from Gecko 1.8, like the Firefox 1.5 release. This testing release also incorporates our new [http://www.mozilla.org/projects/seamonkey/artwork.html Logo Artwork] for the first time.
* SeaMonkey 1.0 is planned to be shipped off the Gecko 1.8.0 branch, which might get a few security/stability fixes, but no big changes from what we shipped with beta. ''We now have [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8.0/ 1.0 nightly builds]; please help us testing them!''

The release processes are managed by the SeaMonkey Council, Chris Thomas is the release engineer in charge of that process.

The QA work needed for releases is overseen by our QA lead Andrew Schultz.

== Release Checklist(s) ==

from n.p.m.seamonkey (written by bz):

> Without me knowing well what is involved in "pushing out a release"

At least:

1) Tagging the trunk at some point when it's stable (coordinating this with
other trunk Gecko/etc consumers, one hopes).
2) Lots of organized and thorough testing of the branch you created.
3) Filing bugs based on the results of that testing.
4) Getting said bugs fixed on that branch.
5) Writing release notes.
6) Creating builds from the branch.
7) Pushing those builds to the FTP server.
8) Announcing the release.

Asa, please chime in if I missed something through ignorance?

I suspect step #2 is somewhat time-consuming, as are step #4 and step #5.

-Boris

Quoting Ben Goodger from IRC:
<ben_> so here's what you need to do to ship a release.
1. decide what you want out of it (a good start is to develop a product plan in
wiki.mozilla.org with checkmarked features/etc)
2. find engineers to do each of the items in the aforementioned list
3. get those engineers to provide blurb+swag for each - this is a description of
the item + estimated time to completion or an ETA.
4. have them implement the features.
5. deal with bugs that arise, manage the
<ben_> 6. when your features are done, you can beta... when you get to a low level of
remaining bugs, you can kick off the final release process.
<Callek> ben_ 5. Deal with bugs that arise, manage the ...??? (cut off)
<ben_> the final release process involves things like documenting changes (release noets,
product pages, etc).
<ben_> er, "manage them using bugzilla flags, etc. prioritize them and have people
work on those."
<ben_> ... getting testing builds spun, having interested users test them and submit feedback,
driving the list to zero and handling new bugs as they come in.
<ben_> Asa probably has more info on the latter half of this process.
<ben_> but what I would suggest starting with is saying, "what do we want from Seamonkey 1.8?"
<ben_> and start listmaking in wiki.mozilla.org
<ben_> you need to identify the work involved in that task then
<ben_> break it down into pieces
<ben_> findpeople to help and get estimates.

[[MozillaReleaseChecklist]]

We'd really like to know what can be done by which people (perhaps some of those tasks can still be done or helped with by MoFo, but it seems we can't rely on that any more).

== QA ==
[http://testrunner.mozilla.org Testrunner] has testcases for the browser UI; the list should probably be extended to cover more functionality. It would be good to run at least basic tests regularly, to catch regressions early. Before the release, more extensive test runs should be performed.

== Features ==
* Current Gecko - many improvements since Mozilla 1.7
* Ship a final release with the various UI improvements since Mozilla 1.7
* Port frontend for [https://bugzilla.mozilla.org/show_bug.cgi?id=2920 Bug 2920] (Delete attachment from mail message in folder) to MailNews
** done
* Port Thunderbird's Inline Spell Checker frontend patch ([https://bugzilla.mozilla.org/show_bug.cgi?id=278310 Bug 278310]) to MailNews
** done
* Revisit the Autoscroll issue. ([https://bugzilla.mozilla.org/show_bug.cgi?id=22775 Bug 22775]])
** done
* Nice splash-screen
** done
* Enable [http://weblogs.mozillazine.org/tor/ SVG] and Cairo ([https://bugzilla.mozilla.org/show_bug.cgi?id=294182 Bug 294182])
** done

For SeaMonkey 1.5:

* Enable calendar ([https://bugzilla.mozilla.org/show_bug.cgi?id=182076 Bug 182076])
** still too unstable to enable
** You may use the [http://www.mozilla.org/projects/calendar/download.html#download_appsuite Calendar extension] for nightly SeaMonkey 1.0 builds on Windows
* Enable MNG again ([https://bugzilla.mozilla.org/show_bug.cgi?id=18574 Bug 18574])
** this can only be done when the source is in mozilla.org tree, which hasn't happened yet
** we will likely have contributed builds with MNG support from Alexander Opitz
* Port to toolkit ([https://bugzilla.mozilla.org/show_bug.cgi?id=255807 Bug 255807])
* Extension Manager ([https://bugzilla.mozilla.org/show_bug.cgi?id=272429 Bug 272429])
* Unattended install for corporate deployment ([https://bugzilla.mozilla.org/show_bug.cgi?id=268740 bug 268740])
* SPNEGO support ([https://bugzilla.mozilla.org/show_bug.cgi?id=246861 Bug 246861])
* Use 7-zip compression for builds ([https://bugzilla.mozilla.org/show_bug.cgi?id=154965 Bug 154965])
* Allow to easily migrate from/to Firefox/Thunderbird ([https://bugzilla.mozilla.org/show_bug.cgi?id=63389 Bug 63389])
* Port Thunderbird RSS/Atom reader to SeaMonkey ([https://bugzilla.mozilla.org/show_bug.cgi?id=255834 Bug 255834]])
* Port Live Bookmarks to SeaMonkey ([https://bugzilla.mozilla.org/show_bug.cgi?id=240393 Bug 240393])
* Enable XForms ([https://bugzilla.mozilla.org/show_bug.cgi?id=305395 Bug 305395 ])
* Improve the default theme (e.g. perhaps make Modern the default theme, see [https://bugzilla.mozilla.org/show_bug.cgi?id=218329 Bug 218329])
* Backout bug [https://bugzilla.mozilla.org/show_bug.cgi?id=281402 Bug 281402](or part of it) to re-enable Xprint under GTK2+ builds
** biesi: can't xprint still be enabled? should be as simple as --enable-xprint, right?
** ajschult: Yes. The biggest issue there is that Red Hat / Fedora no longer install libXp.so by default ([https://bugzilla.mozilla.org/show_bug.cgi?id=284444 bug 284444]). It'd need to be dynamically loaded.
* Improve CSS rules for Message Grouping. Something like [https://bugzilla.mozilla.org/show_bug.cgi?id=263255 Bug 263255]
* Disable IM button or add IM capability ([https://bugzilla.mozilla.org/show_bug.cgi?id=214223 Bug 214223] and [https://bugzilla.mozilla.org/show_bug.cgi?id=218714 Bug 218714])

...feel free to fill in more...

[[Talk:SeaMonkey:First_Release|Talk about this]]

SeaMonkey/QA

2005-09-10T18:07:01Z

Ajschult: add link to testrunner page

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page. At this point, we are particularly interested in getting smoketesters.

== SeaMonkey QA Call to Action ==

As we approach our first [[SeaMonkey:Home_Page|SeaMonkey]] release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

In preparation for this first release, we need as many testers as possible to download and use recent nightly Gecko 1.8 branch builds. Until these are available, testers should use the last trunk build before the branch was created ([http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-08-12-06-trunk/ Windows and Linux], [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-08-12-12-trunk/ Mac]). Testers who wish to test all the latest changes in preparation for a second release should download and use [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ recent nightly trunk builds]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7, and bugs in recent trunk builds that do not exist on the 1.8 branch or in the August 12 builds), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&version=1.8+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&version=1.8+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* '''Smoketests''' should be run regularly using [[SeaMonkey:QA:Testrunner|testrunner]] to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity. If you run the smoketests regularly, please add your name to the [[SeaMonkey:QA_Areas|QA Areas]] page. Please stop by [irc://moznet/seamonkey #seamonkey] for more about using testrunner.

* Work on an area identified by a developer as needing special attention, as identified on the [[SeaMonkey:QA_Wanted|QA Wanted]] page.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

* If you find a bug that you believe must be fixed before the next milestone (1.0a), nominate the bug to block release by setting the "blocking-seamonkey1.0a" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B bugs] the Council has already decided should block the next milestone.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] and [irc://irc.mozilla.org/bugs #bugs] generally have a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

* The [http://weblogs.mozillazine.org/seamonkey-qa/ SeaMonkey QA blog] will contain announcements of any changes in SeaMonkey QA needs.

SeaMonkey:QA:Testrunner

2005-09-10T18:01:11Z

Ajschult: initial version, mostly by opi

== How we want organize Testrunner testing ==

We will use testrunner on http://www2.le-bit.de/bugzilla to manage the testrunns.

We will have 2 groups. The managers group can edit the testcases and manage the testruns. The runners group can run the testruns and mark them ok or failed.

The managers group will start new runs periodicaly or after request on IRC.

The runners group can work through the open testcases. Please look into the name of the testrun and ensure it is for YOUR system and that you test with the same Build ID. If you would like to run a testrun that do not exists, ask one in the managers group to start one.

If a testcase (one task out of the testrun) does not work properly, search bugzilla for an existing bugreport. If no such bug exists, file a new bug, add the "smoketest" keyword. But '''do not use''' the bugzilla system on the testrunner server use the normal [https://bugzilla.mozilla.org/ https://bugzilla.mozilla.org/] but leave a note in bug and on the testcase that failed.

== About starting testruns ==

Naming schema for starting testruns:

" SeaMonkey [trunk/branch] $buildid [Linux gtk1|Linux gtk2|Win95|Win98|WinME|Win2000|WinXP|MaxOSX 10.4]"
Maybe something else as System (like Linux gtk2 MNG).
The $buildid can be read out of the directory where the install files/package lay out or from the window title bar.

Please run the SeaMonkey Nightly and the SeaMonkey Alpha Milestone plan in rotating way for the testruns you start.

== Managers Group ==

Andrew Schultz (ajschult), Alexander Opitz (opi), Carsten Book (Tomcat)

== Testers Group ==

SeaMonkey/QA

2005-09-10T04:57:20Z

Ajschult: /* More QA Resources */

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page. At this point, we are particularly interested in getting smoketesters.

== SeaMonkey QA Call to Action ==

As we approach our first [[SeaMonkey:Home_Page|SeaMonkey]] release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

In preparation for this first release, we need as many testers as possible to download and use recent nightly Gecko 1.8 branch builds. Until these are available, testers should use the last trunk build before the branch was created ([http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-08-12-06-trunk/ Windows and Linux], [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-08-12-12-trunk/ Mac]). Testers who wish to test all the latest changes in preparation for a second release should download and use [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ recent nightly trunk builds]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7, and bugs in recent trunk builds that do not exist on the 1.8 branch or in the August 12 builds), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&version=1.8+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&version=1.8+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity. If you run the smoketests regularly, please add your name to the [[SeaMonkey:QA_Areas|QA Areas]] page.

* Work on an area identified by a developer as needing special attention, as identified on the [[SeaMonkey:QA_Wanted|QA Wanted]] page.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

* If you find a bug that you believe must be fixed before the next milestone (1.0a), nominate the bug to block release by setting the "blocking-seamonkey1.0a" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B bugs] the Council has already decided should block the next milestone.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] and [irc://irc.mozilla.org/bugs #bugs] generally have a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

* The [http://weblogs.mozillazine.org/seamonkey-qa/ SeaMonkey QA blog] will contain announcements of any changes in SeaMonkey QA needs.

SeaMonkey/QA

2005-07-08T05:37:11Z

Ajschult: add a link to new QA Wanted page

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page. At this point, we are particularly interested in getting smoketesters.

== SeaMonkey QA Call to Action ==

As we approach our first [[SeaMonkey:Home_Page|SeaMonkey]] release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

In preparation for this first release, we need as many testers as possible to download and use [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ recent nightly trunk builds]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity. If you run the smoketests regularly, please add your name to the [[SeaMonkey:QA_Areas|QA Areas]] page.

* Work on an area identified by a developer as needing special attention, as identified on the [[SeaMonkey:QA_Wanted|QA Wanted]] page.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

* If you find a bug that you believe must be fixed before the next milestone (1.0a), nominate the bug to block release by setting the "blocking-seamonkey1.0a" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B bugs] the Council has already decided should block the next milestone.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] and [irc://irc.mozilla.org/bugs #bugs] generally have a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

SeaMonkey/QA Areas

2005-05-14T23:42:44Z

Ajschult: update bug day info

There are several areas that need Quality Assurance attention. The purpose of this page is to identify who is working in what areas. This will allow us to know what areas we have covered and where we need to recruit more volunteers. Please add you name and email to the appropriate area.

=== Bug Triage ===
If you are active in triage of SeaMonkey bugs (front end or back end), add yourself to this section, along with what area and operating system (if any) you focus on. Putting your name here might get you CC'd occaisonally to help diagnose a bug affecting your area/platform.

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"
! Name and email
! Bug triage area
! OS
|-
| Andrew Schultz[mailto:ajschult@verizon.net '' '']
| everything :)
| Linux
|-
| Dave Murray (irongut)[mailto:irongut@vodafone.net '' '']
| everything
| Win2k, WinXP
|-
| Carsten Book (Tomcat)[mailto:carstenbook@gmail.com '' '']
| everything (incl Mail/News/IMAP)
| Win2k, WinXP, Windows 2003 Srv
|-
| Charles Fenwick [mailto:clf03f@fsu.edu '' '']
| no speciality
| WinXP, Linux
|-
| Stefan Hermes [mailto:stefan_h@hem.utfors.se '' '']
|
| Mac OS X
|-
| Justin Wood (Callek)[mailto:116057@bacon.qcc.mass.edu '' '']
| My best at everything, (No Proxy or IMAP) QA
| Win32 (XP)
|-
| Adam Hauner (AHA)[mailto:aha@czilla.cz '' '']
| crashes
| WinXP
|}

=== Smoketests ===
If you run the [http://www.mozilla.org/quality/smoketests/ smoketests] regularly (at least once a week) add yourself to the list for the OS that you run the tests on.

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse;"
! OS
! Name and email
|-
| Windows
| Carsten Book(Tomcat) Smoketests/Testrunner [mailto:carstenbook@gmail.com '' '']
|-
| Linux
|
|-
| Mac OS X
|
|}

=== Bug Day ===
'''update''': Bug day has evolved into a 24-7 affair, so this became a bit less relevant. The fun is still happening in [irc://irc.mozilla.org/bugs #bugs] and we'd still like to have a more structured Bug Day once we have a milestone released. More information as it becomes available...

:We would like to have experienced SeaMonkey QA help run Bug Day activities. They occur in [irc://irc.mozilla.org/bugs #bugs] on Tuesdays as long as there is sufficient community interest to make it happen. We'd also like to have larger Bug Days after releases (including beta versions). If you can help out, add yourself below with what times you would likely be available (Mozilla time zone (Pacific)) on Tuesdays.

{| border="1" cellspacing="0" cellpadding="5" style="margin-left: 15px; border-collapse:collapse;"
! Name and email
! When I can help
|-
| Andrew Schultz[mailto:ajschult@verizon.net '' '']
| 4pm-10pm
|-
| Dave Murray (irongut)[mailto:irongut@vodafone.net '' '']
| 10:00 - 15:00 (19:00 - 00:00 UK Time)
|-
| Carsten Book (Tomcat)[mailto:carstenbook@gmail.com '' '']
| 10:00 - 15:00 PST
|}

SeaMonkey/QA

2005-04-02T22:53:16Z

Ajschult: we need smoketesters!

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page. At this point, we are particularly interested in getting smoketesters.

== SeaMonkey QA Call to Action ==

As we approach our first [[SeaMonkey:Home_Page|SeaMonkey]] release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity. If you run the smoketests regularly, please add your name to the [[SeaMonkey:QA_Areas|QA Areas]] page.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

* If you find a bug that you believe must be fixed before the next milestone (1.0a), nominate the bug to block release by setting the "blocking-seamonkey1.0a" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B bugs] the Council has already decided should block the next milestone.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

Talk:SeaMonkey/QA Areas

2005-04-01T05:18:37Z

Ajschult: add some responses and rearrange

AJ, or someone, could you give us green horns a rundown on QA, please? [[User:L Squared|L2]] 06:24, 30 Mar 2005 (PST)

What is triage, exactly?

::And Triage Bugs is (i think) selecting the unconfirmed Bugreports into confirmed, WFM, invalid and so on --[[User:Tomcat|Tomcat]] 14:14, 30 Mar 2005 (PST)

::Right. In general, triage is making sure open bugs are valid and have enough information for developers to fix. We usually have to also go through NEW bugs as many bugs wind up in the wrong component or get submitted as NEW when they should be UNCONFIRMED. And sometimes we have to go back through old reports and see if the bugs still are still problems. [[User:Ajschult|Ajschult]] 21:18, 31 Mar 2005 (PST)

I gather that a smoke test is a precise series of steps to check a build.

::Exactly. They're designed to make sure builds are at least usable for developers and QA members. This role has always been fulfilled by Netscape and then Mozilla Foundation employees, so we're looking for new people to run through the tests. If you can use the suite, you can help out with smoketests! [[User:Ajschult|Ajschult]] 21:18, 31 Mar 2005 (PST)

What is a bug day?

:: There is a good Page explaining what Bugday is http://bugday.moznetwork.org/ its about confirming unconfirmed bugs :-)--[[User:Tomcat|Tomcat]] 14:14, 30 Mar 2005 (PST)

Are results entered in bugzilla?

::Results of what? I think the answer is yes. :) Bugs discovered during smoketests are entering in bugzilla. And the point of bug day is to accomplish something in bugzilla.

SeaMonkey/QA

2005-03-26T06:42:12Z

Ajschult: add bit about blocking flags

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page.

== SeaMonkey QA Call to Action ==

As we approach our first SeaMonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

* If you find a bug that you believe must be fixed before the next milestone (1.0a), nominate the bug to block release by setting the "blocking-seamonkey1.0a" nomination flag to "?" and add a comment to state why you think the bug is important. Also, please help with any QA needed for the [https://bugzilla.mozilla.org/buglist.cgi?product=Mozilla+Application+Suite&resolution=---&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey1.0a%2B bugs] the Council has already decided should block the next milestone.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

SeaMonkey/QA

2005-03-26T02:41:59Z

Ajschult: add link to new QA Areas page

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page.

== SeaMonkey QA Call to Action ==

As we approach our first SeaMonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

SeaMonkey/QA

2005-03-26T02:41:59Z

Ajschult: add link to new QA Areas page

If you are actively triaging bugs, running smoketests or would like to help out with Bug Days, add yourself to the [[SeaMonkey:QA_Areas|QA Areas]] page.

== SeaMonkey QA Call to Action ==

As we approach our first SeaMonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

SeaMonkey/QA Areas

2005-03-26T02:21:00Z

Ajschult: initial version

SeaMonkey/QA

2005-03-23T16:00:42Z

Ajschult: SeaMonkey

== SeaMonkey QA Call to Action ==

As we approach our first SeaMonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the SeaMonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id SeaMonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== SeaMonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the SeaMonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

SeaMonkey/QA

2005-03-21T05:02:34Z

Ajschult: add additional QA tasks

== Seamonkey QA Call to Action ==

As we approach our first Seamonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the Seamonkey community to help with quality assurance by testing current builds to identify and report bugs, and help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Seamonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== Seamonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the Seamonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== Additional QA Tasks ==

In addition to filing bugs and triaging unconfirmed bug reports, there are other QA areas that need attention.

* '''Crash bugs''' are some of the worst bugs and deserve special attention. You can retrieve talkback stacks for specific bugs using the talkback ID at this [http://talkback-public.mozilla.org/talkback/fastfind.jsp query page]. You can also browse submitted [http://talkback-public.mozilla.org/reports/mozilla/ talkback reports] to look for common crashes. If you can reproduce the crash based on the information the submitter provided and can't find an existing bug, please file a new bug.

* [http://www.mozilla.org/quality/smoketests/ '''Smoketests'''] should be run regularly to catch serious regressions quickly. If you find a smoketest that fails and can't find an existing bug, please file a new bug with the keyword ''smoketest'' and ''blocker'' severity.

* Developers flag bugs with the '''qawanted''' keyword to indicate that they need help to properly diagnose a problem. This can mean writing a testcase, testing on a specific platform, or just trying to find consistent steps to reproduce a bug. You can search for bugs with the ''qawanted'' keyword from the [https://bugzilla.mozilla.org/query.cgi bugzilla query] page (advanced search).

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks who can help you getting started with bug reporting or triage.

SeaMonkey/QA

2005-03-18T08:25:50Z

Ajschult: add testcase link

== Seamonkey QA Call to Action ==

As we approach our first Seamonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the Seamonkey community to help with quality assurance by testing current builds to identify and report bugs and by help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Seamonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If more information is needed, add a comment in the bug asking the reporter for the information needed. Also remember that Gecko/layout bugs need a [http://www.mozilla.org/newlayout/bugathon.html testcase] before they can be confirmed. Once the bugs are properly triaged, 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.

== Seamonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the Seamonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks that can help you getting started with bug reporting or triage.

SeaMonkey/QA

2005-03-18T08:11:58Z

Ajschult: add gecko bugs query link

== Seamonkey QA Call to Action ==

As we approach our first Seamonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the Seamonkey community to help with quality assurance by testing current builds to identify and report bugs and by help sorting out bugs that have already been filed.

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]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html file a new bug]. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the ''regression'' keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Seamonkey bugs] and [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Core&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=2005-01-12&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id Gecko core bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html triaged]. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If not enough information is available, add a comment in the bug asking the reporter for the information needed. Once the bugs are properly triaged, 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.

== Seamonkey vs. Gecko bugs ==

There are two major classes of bugs you might find in the Seamonkey Suite:

* '''Front-end bugs''': These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Application%20Suite Mozilla Application Suite components].

* '''Back-end bugs''': These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core core Gecko components], which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

== More QA Resources ==

* [http://www.mozilla.org/quality/help/ Helping with QA] provides a good overview of the various tasks for people getting involved in QA.

* [http://www.mozilla.org/quality/ Mozilla's QA Home Page] provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

* [irc://irc.mozilla.org/seamonkey #seamonkey] generally has a few developers or experienced QA folks that can help you getting started with bug reporting or triage.

SeaMonkey/QA

2005-03-17T05:11:00Z

Ajschult: style cleanup

SeaMonkey:Home Page

2005-03-16T17:42:58Z

Ajschult: link to new QA page (old content is there)

{{SeaMonkey-Resources}}

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.

[http://www.mozilla.org/seamonkey-transition.html MoFo Transition Plan Announcement]

[http://web.mit.edu/bzbarsky/Public/SeaMonkey.txt Boris Zbarsky's Open Letter]

== The plan ==
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.

Our [[SeaMonkey:Project Goals|Project Goals]] document describes where the project is basically headed.

For one thing, we have to get a [[SeaMonkey:First Release|first release]] out the door.

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.

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.
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 [[User:Biesi|Biesi]]

== The team ==

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.

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

== Meetings ==

The next official meeting on [irc://irc.mozilla.org/seamonkey IRC] is on '''Tuesday March 22nd 2005 at 17:00 UTC.'''

SeaMonkey/QA

2005-03-16T17:33:46Z

Ajschult: add QA page

SeaMonkey/Supporters

2005-03-08T05:38:38Z

Ajschult: