Release Management/Tracking rules

From MozillaWiki
Jump to: navigation, search

This document is a draft.

This page describes the rules applied by the Release Team to track or not a bug for a release.

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.


Regression

If the bug is a important regression, then release management will track the bug and follow up with developers to get it fixed and in affected releases as soon as possible.

Sometimes, the keyword 'regression' is not set but the previous version is marked as unaffected and the current version as affected. In this case, please add the 'regression' keyword.

Not a regression

When dealing with new features, this case is common.

Tracking is recommended if:

  • The bug is a crash (or fix a crash). For example, bugs with keyword topcrash* are usually tracked.
  • Impact web compatibility
  • Add-on compatibility implications
  • Introduced a new feature which may need to be backed out
  • The bug is sec-critical (or maybe sec-high as well; we should at least triage sec-high)

If there is no patch on a critical bug report, the tracking is recommended.

If the patch has already landed in Mozilla-central for a few days and an uplift requests has been filled (or already applied), tracking is not necessary (except for high risk changes).

Misc

The tracking flag tracking-fennec is not managed by the release team. This flag is used by the mobile team.

Disabling a Feature

  • separate bugs for "disable feature X" are always clearer than attaching patches/getting approvals in meta or other bugs with confusing summaries (e.g. it's hard to tell that bug 994589 resulted in a feature disabling after the fact without hunting through the comments, that bug is tracking something else overall)
  • the "disabled" value of the status flags should be set on bugs whose functionality is being disabled, not on bugs where the disabling took place. For example, in this case, bug 619558 (and maybe other trackers?) should be marked "status-firefox31: disabled" (the feature is disabled on 31), and bug 994589 should be marked as "status-firefox31: fixed" (the crashes are fixed by the disabling - a comment indicating that is also useful).