MDN/Archives/Projects/Development/CompatibilityTables/Milestones: Difference between revisions

MDN/Archives/Projects/Development/CompatibilityTables/Milestones (view source)

2 bytes removed , 16 February 2016

Confirmed users

630

edits

@@ 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:
-# '''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).
+# '''Frozen''': <br>When a milestone is ''frozen'', 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. 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.