255
edits
BMO/UserGuide: Difference between revisions
→Tracking Flags: Updating Flag info
Diannasmith (talk | contribs) (→Status Flags: adding correct link) |
Diannasmith (talk | contribs) (→Tracking Flags: Updating Flag info) |
||
| Line 89: | Line 89: | ||
The whiteboard field is for free tagging. It's used both by teams and by people who want to track bugs they're interested in. | The whiteboard field is for free tagging. It's used both by teams and by people who want to track bugs they're interested in. | ||
== | == All about Flags == | ||
[[File:Status.png|400px|right]] | |||
=== tracking-firefoxXX === | |||
''Who's doing the tracking? Should i even set these flags?'' | ''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. | 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. A tracking flag shows whether a bug is being investigated for possible resolution in the Firefox XX release. Bugs marked tracking-Firefox XX are bugs that must be resolved one way or another before a particular release ships. [[Firefox/Drivers|Release drivers]] will track and shepherd the bug until it is determined the bug no longer impacts the release. | ||
[[File:Tracking-flag-example.png|thumb]] | [[File:Tracking-flag-example.png|thumb]] | ||
| Line 118: | Line 120: | ||
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. | 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. | ||
Refer to [http://web.archive.org/web/20160417051846/https://blog.mozilla.org/channels/2011/06/01/more-details-about-how-to-use-the-tracking-firefox-bugzilla-flag/ these guidelines] on setting the tracking flag. | |||
=== status-firefoxXX === | |||
A flag which represents the status of the bug with respect to Firefox XX. | |||
{| class="wikitable" | |||
|+ status-firefoxXX | |||
|- | |||
| --- || We don't know whether Firefox XX is affected | |||
|- | |||
| ? || We don't know whether Firefox XX is affected, but we want to find out | |||
|- | |||
| unaffected || This bug does not affect Firefox XX | |||
|- | |||
| affected || This bug affects Firefox XX | |||
|- | |||
| fix-optional || This bug affects Firefox XX, we would take a fix but don't consider it as release blocking | |||
|- | |||
| fixed || This bug is fixed in Firefox XX | |||
|- | |||
| verified || This bug is fixed and verified in Firefox XX | |||
|- | |||
| disabled || This feature is disabled in Firefox XX | |||
|- | |||
| verified disabled || Disabling the feature is verified in Firefox XX | |||
|- | |||
| wontfix || A fix for this bug will not be accepted in Firefox XX | |||
|- | |||
|} | |||
'''Approval Flags''': Set on the attachment of a bug | |||
All patches landing on ''mozilla-beta/release/esr'' branches must have these nominated by setting a ''''' ? ''''' flag. <br>Please make sure to fill in the populated list of questions '''[Approval Request Comment]''' that come up on the attachment. | |||
This helps Release Management understand the user impact & the risk/reward analysis before we grant or deny approval. If this form is left incomplete it will be sent back to you for completion. | |||
[[File:ApprovalRequest.png|750px|centre]] | |||
== Status Flags == | == Status Flags == | ||