? bug-for-every-change.patch.txt ? feature-freeze-v2.patch.txt ? feature-freeze.patch.txt ? limit-lc2-scope.patch.txt ? too-late-for-features.patch.txt ? wg-decision-deadline.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 17:59:35 -0000 @@ -641,14 +641,20 @@
The end of the review period is the cutoff for bugs to be considered as Last Call or Pre-Last Call feedback. Bugs beyond this date will NOT be treated as pre-LC or LC comments (whichever is relevant). The Chairs could grant exceptions on a case-by-case basis, but in general there is no guarantee of a bug filed after the cutoff being settled during the Last Call period. Any such bugs will be considered during a subsequent Last Call, during the Candidate Recommendation phase, or -for a future version of HTML. +for a future version of HTML.
+ +For second and subsequent Last Calls, only comments related to +changes made since the start of the previous Last Call will be +accepted. This is to ensure we do not get into an infinite regress of +new feedback; only new changes will get re-reviewed.
+Therefore during a pre-LC review, or during a Last Call, feature +
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.
+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:
+ +