? feature-freeze.patch.txt
Index: decision-policy-v2.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy-v2.html,v
retrieving revision 1.38
diff -u -r1.38 decision-policy-v2.html
--- decision-policy-v2.html	2 Aug 2011 07:05:55 -0000	1.38
+++ decision-policy-v2.html	10 Apr 2012 03:41:18 -0000
@@ -839,12 +839,31 @@
 arguably a feature addition - even arguably ambiguous cases such as documenting
 longstanding de facto standard features.</p>
 
-<p>Therefore during a pre-LC review, or during a Last Call, feature
+<p>Therefore during a pre-LC review, feature
 additions or removals should only be done with sufficient prior notice
 to the group, in the form of a bug, a WG decision, or an on-list
 discussion. This applies only to LC-track drafts and does not apply to
 drafts that may include material for future versions of HTML.</p>
 
+<p>After the start of Last Call (and through subsequent Last Calls)
+features can only be added to or removed from the specification with
+prior concurrence of the Working Group, in one of the following forms:</p>
+
+<ol>
+<li>A Working Group Decision on a tracker issue, whether a contested decision by
+survey or a consensus decision on a sole provided Change Proposal.
+
+<li>A Call for Consensus of at least one week's duration (longer near
+or during holiday periods), citing a bug that requests the feature
+addition/removal and describes the change in reasonably clear
+terms. Such a Call for Consensus may be initiated by the Chairs, or by
+the Editor of the relevant specification. Any objection to such a CFC
+would require escalation to an issue. Editors are free to simply
+reject feature requests rather than follow this process.
+
+</ol>
+
+
 
 <h3>What kind of changes might this revert policy apply to?</h3>