SeaMonkey/QA: Difference between revisions

Jump to navigation Jump to search
→‎SeaMonkey QA Call to Action: update description of regressions
m (→‎SeaMonkey QA Call to Action: update for SeaMonkey 1.1.1)
(→‎SeaMonkey QA Call to Action: update description of regressions)
Line 13: Line 13:
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.) A 'blocking-seamonkey1.5a' flag has been set up in bugzilla to help keep track of what needs to be done before SeaMonkey 1.5a.  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.5a 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.5a%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.5a%3F yet to be approved bugs] blocking the release.
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.) A 'blocking-seamonkey1.5a' flag has been set up in bugzilla to help keep track of what needs to be done before SeaMonkey 1.5a.  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.5a 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.5a%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.5a%3F yet to be approved bugs] blocking the release.


If you find a problem in any builds of SeaMonkey, 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.
If you find a problem in any builds of SeaMonkey, 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 or SeaMonkey 1.0.x, and bugs in recent trunk builds that do not exist in SeaMonkey 1.1.x), 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 the next SeaMonkey release, 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 the next SeaMonkey release, and what issues need to be reported in the release notes.
213

edits

Navigation menu