? bug-for-every-change.patch.txt
? feature-freeze.patch.txt
? too-late-for-features.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:53:38 -0000
@@ -802,11 +802,16 @@
 review period. Likewise, the W3C Last Call process itself imposses a
 cutoff on the Last Call period.</p>
 
-<p>During such periods, we don't want to call a total stop to useful
-changes that aren't in response to those bugs. But that might create a
-situation where a person or group strongly objects to some change
-after the cutoff, but they don't have automatic recourse through the
-normal bug process.</p>
+<p>During pre-LC review periods, and first Last Calls, we don't want
+to call a total stop to useful changes that aren't in response
+tobugs. But that might create a situation where a person or group
+strongly objects to some change after the cutoff, but they don't have
+automatic recourse through the normal bug process.</p>
+
+<p>Starting with second and later Last Calls, the rate of change
+should slow significantly. At this point, we would expect
+that <em>every</em> change must be in response to a bug filed by the
+relevant Last Call deadline. This is necessary to achieve stability.</p>
 
 <p>Therefore, in exceptional cases, we would ask for a change to be
 reverted from the LC-track draft pending resolution of the issue