Changes

''tracking-firefox-20? Who's doing the tracking? Should i even set these flags?''

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-26 have a ?, +, or - associated.

For example, a [https[File://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox26&list_id=7974674&o1=substring&resolution=Tracking-flag--&resolution=DUPLICATE&query_format=advanced&v1=%2B search for tracking-firefox-26 and "+"example.png|thumb]] currently shows around 50 bugs.

{| class="wikitable"|-! Value !! Meaning|-| --- || Default/Not nominated|-| ? || Bug is nominated for this release|-| + || Bug is tracked for this release|-| - || Bug will not be tracked for this release|-| blocking || Bug is considered a blocker for this release|} Most users will only be able to [[Release_Management/Release_Process#All_about_Flags|More information on nominate a bug for tracking]] by setting the tracking flag for a release to ''?''. The Release Drivers group (which includes Release Management) will respond to the request for tracking. For example, a [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox_beta&o1=equals&v1=%2B search for tracking Firefox Flags]Beta and "+"]would list the bugs which release managers decided to track for the Beta release of Firefox.  If you would like to suggest a bug and its fix be considered (by release managers) for a particular release, edit the bug and set the tracking flag for that release to ''?''. This is often done for a bug that's been fixed in one release channel but needs to be uplifted to another.