BMO/How to Use Bugzilla: Difference between revisions

→‎Bug triage: link to triage documentation
(→‎Bug triage: link to triage documentation)
 
(One intermediate revision by one other user not shown)
Line 203: Line 203:


==Bug triage==
==Bug triage==
[https://mozilla.github.io/bug-handling/triage-bugzilla Bug triage documentation]


==Products and components==
==Products and components==
Line 264: Line 266:
Tracking flags are used by developers, triagers, QA and the release management teams to keep track of bugs whose fixes are slated to go into a particular product release.  Flags of the form tracking-firefox-60 have a ?, +, or - associated.  
Tracking flags are used by developers, triagers, QA and the release management teams to keep track of bugs whose fixes are slated to go into a particular product release.  Flags of the form tracking-firefox-60 have a ?, +, or - associated.  


For example, a https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox60&list_id=14022303&o1=substring&resolution=---&resolution=DUPLICATE&query_format=advanced&v1=%2B and "+"] currently shows around 20 bugs.  
For example, a [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox60&list_id=14022303&o1=substring&resolution=---&resolution=DUPLICATE&query_format=advanced&v1=%2B search for tracking-firefox-60 and "+"] currently shows around 20 bugs.  


If you would like to suggest a bug and its fix be considered (by release managers) for a particular release, mark it with that release and a question mark. This might be good to do for a bug that's been fixed in one release channel but needs to be uplifted to another.
If you would like to suggest a bug and its fix be considered (by release managers) for a particular release, mark it with that release and a question mark. This might be good to do for a bug that's been fixed in one release channel but needs to be uplifted to another.