Confirmed users
630
edits
MDN/Archives/Projects/Development/CompatibilityTables/Milestones: Difference between revisions
Jump to navigation
Jump to search
MDN/Archives/Projects/Development/CompatibilityTables/Milestones (view source)
Revision as of 17:46, 12 February 2016
, 12 February 2016→Milestones lifecycle
| Line 14: | Line 14: | ||
Milestone processing happen when people start working on a milestone content. There are three formal steps while a milestone is in process, each step defines a set of restriction and requirements: | Milestone processing happen when people start working on a milestone content. There are three formal steps while a milestone is in process, each step defines a set of restriction and requirements: | ||
# '''Freezed''': <br>When a milestone is ''freezed'', it is strictly forbidden to add new major bugs to the milestone. This states is possible only if the previous milestone is about ''to be released'' (see below). | # '''Freezed''': <br>When a milestone is ''freezed'', it is strictly forbidden to add new major bugs to the milestone and all new normal bugs should explicitly block a major bug. This states is possible only if the previous milestone is about ''to be released'' (see below). | ||
# '''To be released''': <br>When a milestone is about ''to be released'', it is strictly forbidden to add new normal bugs to the milestone. At that point, adding a new bug to the milestone requires a formal agreement from the accountable and responsible stakeholders. | # '''To be released''': <br>When a milestone is about ''to be released'', it is strictly forbidden to add new normal bugs to the milestone. At that point, adding a new bug to the milestone requires a formal agreement from the accountable and responsible stakeholders. This state is reached automatically if all the major bug of the milestone are resolved. | ||
# '''released''': <br>The work on the milestone is over and the milestone itself is considered "reached" (see below). At that point no new bug, even minor is allowed in the milestone. | # '''released''': <br>The work on the milestone is over and the milestone itself is considered "reached" (see below). At that point no new bug, even minor is allowed in the milestone. | ||
| Line 21: | Line 21: | ||
* All major and normal bugs associated to a milestone are resolved | * All major and normal bugs associated to a milestone are resolved | ||
* The milestone has been formally reviewed (and approved) during the project meeting. | * The milestone has been formally reviewed (and approved) during the project meeting. | ||
* All remaining open bugs (normal or minor) has been reallocated to a next milestone. | |||
== Milestone breakdown == | == Milestone breakdown == | ||