Confirmed users
2,816
edits
Release Management/Tracking rules: Difference between revisions
Jump to navigation
Jump to search
m
Release Management/Tracking rules (view source)
Revision as of 19:20, 11 September 2017
, 11 September 2017minor clarifications for triage
m (Clarifying some triage and flagging issues) |
m (minor clarifications for triage) |
||
| Line 5: | Line 5: | ||
[[Releases/Flags|Tracking flags]] are set to manage a list of release critical bugs but also the bugs / features that the Release Team wants to keep on their radar. | [[Releases/Flags|Tracking flags]] are set to manage a list of release critical bugs but also the bugs / features that the Release Team wants to keep on their radar. | ||
= Regressions = | = Regressions: Status flags + keyword = | ||
*Please mark regressions with the keyword "regression" and the status flag.* | *Please mark regressions with the keyword "regression" and the status flag.* | ||
| Line 11: | Line 11: | ||
That should ensure that the bug will be triaged by relman and a team of engineering managers. | That should ensure that the bug will be triaged by relman and a team of engineering managers. | ||
It will show up on this Release Health dashboard: https://mozilla.github.io/releasehealth/?channel=beta | |||
If the bug is a important regression, and you need to escalate quickly to get help across teams, then you can also request the bug to be tracked by relman. Release management will track the bug and follow up with developers and QE to get it fixed, tested, and in affected releases as soon as possible. Not every regression can or should be tracked. | If you know the bug is a important regression, and you need to escalate quickly to get help across teams, then you can also request the bug to be tracked by relman. Release management will track the bug and follow up with developers and QE to get it fixed, tested, and in affected releases as soon as possible. Not every regression can or should be tracked. | ||
For a very serious issue that would block either a release, or the release of a feature, relman can mark the tracking flag as "blocking". | For a very serious issue that would block either a release, or the release of a feature, relman can mark the tracking flag as "blocking". | ||
= Not a regression = | = Not a regression: Request tracking = | ||
When dealing with new features, this case is common. | When dealing with new features, this case is common. | ||