SeaMonkey/QA: Difference between revisions

43 bytes removed ,  23 February 2006
update for SeaMonkey 1.0.1
(mention bugzilla products)
(update for SeaMonkey 1.0.1)
Line 5: Line 5:
== SeaMonkey QA Call to Action ==
== 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.
As we approach the release of SeaMonkey 1.0.1, we need to ensure that the suite stays in 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.
Testers who wish to test the changes for SeaMonkey 1.0.1, should 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.
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.
213

edits