Difference between revisions of "QA:Home Page"
(→Bug Triage: the page moved) |
(→Bug Triage: re-order this section with an eye to new triagers) |
||
Line 3: | Line 3: | ||
== Bug Triage == | == Bug Triage == | ||
− | [[QA: | + | [[QA:Triage Policies and Procedures]] explains how the triage team goes about its daily work and how it interacts with the larger Mozilla.org triage community. |
− | |||
[[QA:Bugzilla:Searching_For_Dupes]] contains information on how to search Bugzilla for duplicates prior to filing. This information will join the Bugzilla FAQ bug exists here for previewing and discussion. | [[QA:Bugzilla:Searching_For_Dupes]] contains information on how to search Bugzilla for duplicates prior to filing. This information will join the Bugzilla FAQ bug exists here for previewing and discussion. | ||
: Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.) Some of the information developed in this document, however, is intended primarily for triage team members and will likely end up elsewhere (not /support/) on cb.o | : Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.) Some of the information developed in this document, however, is intended primarily for triage team members and will likely end up elsewhere (not /support/) on cb.o | ||
− | |||
− | |||
[[QA:Keywords & Status Whiteboard]] explains some of the commonly-used keywords and status whiteboard entries. | [[QA:Keywords & Status Whiteboard]] explains some of the commonly-used keywords and status whiteboard entries. | ||
[[QA:Hardware Configurations]] is a mostly-complete list of hardware available to each QA or developer, useful when seeking patch testing or triage in a certain configuration. | [[QA:Hardware Configurations]] is a mostly-complete list of hardware available to each QA or developer, useful when seeking patch testing or triage in a certain configuration. | ||
+ | |||
+ | [[QA:Bugzilla:FAQ]] contains the most recent version of our [http://www.caminobrowser.org/support/bugzilla/ Bugzilla FAQ]. This wikified version is the pre-cb.o version to allow discussion of the proposed changes. (See [[User:Sardisson/To_Do]] for some initial thoughts on things to add.) | ||
+ | : Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.) | ||
== Release Testing == | == Release Testing == |
Revision as of 02:46, 26 September 2006
Contains information on Camino's quality assurance procedures, including triaging bugs and testing the Camino application itself.
Bug Triage
QA:Triage Policies and Procedures explains how the triage team goes about its daily work and how it interacts with the larger Mozilla.org triage community.
QA:Bugzilla:Searching_For_Dupes contains information on how to search Bugzilla for duplicates prior to filing. This information will join the Bugzilla FAQ bug exists here for previewing and discussion.
- Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.) Some of the information developed in this document, however, is intended primarily for triage team members and will likely end up elsewhere (not /support/) on cb.o
QA:Keywords & Status Whiteboard explains some of the commonly-used keywords and status whiteboard entries.
QA:Hardware Configurations is a mostly-complete list of hardware available to each QA or developer, useful when seeking patch testing or triage in a certain configuration.
QA:Bugzilla:FAQ contains the most recent version of our Bugzilla FAQ. This wikified version is the pre-cb.o version to allow discussion of the proposed changes. (See User:Sardisson/To_Do for some initial thoughts on things to add.)
- Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.)
Release Testing
QA:Release Testing describes the smoketests that should be performed on release candidate builds to make sure everything is functional before releasing (coming soon).
This page has been protected from editing.