SeaMonkey/QA/Triage HowTo: Difference between revisions

* Start your new SeaMonkey as follows (at a command-line [shell] prompt, after cd to the directory containing the executable):<pre>./seamonkey -no-remote -ProfileManager</pre> The first time, create a new profile then use it. Later on, you can just reuse that same profile.

[https://bugzilla.mozilla.org/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=SeaMonkey&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap This table] tells you how many bugs are '''open but not yet ASSIGNED''' for each SeaMonkey component. Each of the numbers in the table is a link to a list of bugs. This time we'll concentrate on the Components which have the most open bugs (more than 100 to more than 700). They are listed below in decreasing order ("more than 700 at top, down to "just over 100" at bottom). The numbers are as of 2012-08-07 16:00 UTC:

* &nbsp;733 [https://bugzilla.mozilla.org/buglist.cgi?list_id=3958587;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=REOPENED;component=MailNews%3A%20Message%20Display;product=SeaMonkey MailNews:Message Display]

* 1870 [https://bugzilla.mozilla.org/buglist.cgi?list_id=3958668;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=REOPENED;component=Bookmarks%20%26%20History;component=Composer;component=General;component=MailNews%3A%20Message%20Display;component=Preferences;component=UI%20Design;product=SeaMonkey All of the above]

Now what shall we do with all these bugs?

* Is the bug '''in the right Component'''? or even in the right Product? Bugs which affect SeaMonkey can belong in any of the following Products (clicking each link will give you a list of Components, explaining briefly what each of them is for). Most SeaMonkey bugs go in the Products near the top of this list:

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=SeaMonkey SeaMonkey] (anything specific to SeaMonkey, and all SeaMonkey frontend bugs other than those for the Addons Manager)

* Is the bug a '''valid''' bug? If the behaviour it describes is intentional, then the bug is INVALID. If the problem is not a Mozilla problem (if the fault is in an extension, or in the code for some plugin, etc.) the bug is also INVALID but in this case the problem should be reported to the responsible party (the extension author, the plugin makers, etc.)

* Is the bug a real bug or enhancement request, but one '''not worth fixing'''? Only an owner or peer of the component where the bug is found can decide to resolve it WONTFIX. Check [http://www.seamonkey-project.org/dev/project-areas the SeaMonkey project areas page] and/or [[Modules|the Mozilla module owners list]] to see who is in charge. Hopefully some of them will take part in the event so you can ping them.

* Finally, do you think '''you can fix''' the bug? <span style="color:white; background-color:#0C0">Don't panic!</span>. Some of them, including very easy one-liners, will have '''<tt>[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=SeaMonkey%20open%20%22good%20first%22&sharer_id=104443&list_id=4088742 &#91;good first bug&#93;]</tt>''' in the Whiteboard, usually with [language= (meaning the programming language) and [mentor= (with the IRC nick of someone to ask help from); and <span style="background-color:#9F9">even if you aren't yet capable of fixing any single bug, all the above will still need to be done.</span>

** If you think you can fix some particular bugs, "take" them by clicking <take> on the '''Assigned to:''' line in the bug header, and also set the bug status to ASSIGNED at the very bottom.

*** and other pages linked from there. Also don't forget to use '''<tt>hg help</tt>''' to get the Mercurial online help.

Here are the main Resolutions you will probably use. (There are others.)

* '''DUPLICATE''' — This bug is a duplicate of some other bug, whose bug number must be mentioned.

* Also, the '''VERIFIED''' status means that someone other than whoever set RESOLVED has checked that the Resolution is correct. For FIXED bugs, this means in principle that someone (not necessarily the same person) has verified that in recent builds, the bug has disappeared from all three of Windows, Linux and Mac, or at least from those of the three where the bug had been seen before.

* As said earlier, please mark '''all''' bugs handled during this Event by adding <span style="color:white; background-color:#963">[2012&nbsp;Fall&nbsp;Equinox]</span> to the Whiteboard. One of the entries below may be added '''in addition''' if it is not clear that the bug should be RESOLVED immediately.

** '''DUPEME''' — you remember seeing a bug somewhere, of which this bug is a duplicate, but you can't find the other bug back.

**** '''2.''' Some developers have a "Bugzilla address of record" different from their listed email address. Make sure that you have JavaScript enabled (at least on bugzilla.mozilla.org), and use the Bugzilla autocomplete feature in the Cc field of the bug.

Here we'll talk only about the "status-seamonkey-&lt;something&gt;" flags. These are on the right side of the bug page heading, lower than the Cc list. They are used to track in which versions of SeaMonkey the bug has been seen, and also on which branch it has been fixed. (RESOLVED FIXED means the bug is fixed on trunk, even if the fix hasn't yet been ported to the branches.)

* <tt>unaffected</tt> : the bug never occurred in this version.