SeaMonkey/QA/Triage HowTo: Difference between revisions

* 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)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=MailNews%20Core MailNews Core] (backend bugs affecting both SeaMonkey and Thunderbird)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=Toolkit Toolkit] (This includes, among others, all Addon Manager bugs, the bugs for the Firefox-style Download Manager but not the Jökulsárlón one, Password Manager bugs, etc.)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=Core Core] (backend bugs affecting all three of Firefox, Thunderbird and SeaMonkey, especially about HTML page layout)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=Plugins Plugins] (i.e. Acrobat, Flash, Java, and the like)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=Other%20Applications Other Applications] (among others, ChatZilla and DOM Inspector, both of which are included in official versions of SeaMonkey)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Localizations Mozilla Localizations] (bugs about menus & messages in other languages than en-US)

** [https://bugzilla.mozilla.org/describecomponents.cgi?product=NSS NSS] and [https://bugzilla.mozilla.org/describecomponents.cgi?product=NSPR NSPR] (these two change very little, only very few new bugs belong in them)

* Is the bug '''still found''' in current SeaMonkey versions (latest release, latest beta, latest Aurora nightly, latest comm-central-trunk nightly)? If you can't decide, add a comment to the bug asking the reporter, and in that case also add [CLOSEME yyyy-mm-dd INCO] or [CLOSEME yyyy-mm-dd WFM] (where yyyy-mm-dd is a "reasonably" future date) to the Whiteboard.

** '''Note:''' If the bug "depends" on some other open bug (as shown near the top of the bug page), it is normal for it to wait for that oher bug to get FIXED. In that case, asking whether it is still found can wait.

* 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.)

** If the bug is an OS bug (e.g. in X11 or GTK) or a bug in some popular third-party site (Facebook, Google, …) then it is also not a Mozilla bug but coding a temporary workaround might be useful for SeaMonkey users. Ask the developers (as for a WONTFIX, see below).

* Is the bug a real bug or enhancement request, but one '''not worth fixing'''? <span style="background-color: #C00; color: white">Only an owner or peer of the component where the bug is found can decide to resolve it WONTFIX.</span> 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.