W3C home > Mailing lists > Public > public-html-commits@w3.org > August 2012

html5/decision-policy decision-policy-v3.html,1.2,1.3

From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 13 Aug 2012 17:06:53 +0000
To: public-html-commits@w3.org
Message-Id: <E1T0y6P-0006ZL-5h@lionel-hutz.w3.org>
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv24810

Modified Files:
	decision-policy-v3.html 
Log Message:
Change decision apply period to a week
Add an escape clause to bug scope
move all LC2 additions to a single section


Index: decision-policy-v3.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy-v3.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- decision-policy-v3.html	13 Aug 2012 16:42:46 -0000	1.2
+++ decision-policy-v3.html	13 Aug 2012 17:06:51 -0000	1.3
@@ -342,8 +342,8 @@
 will be recorded in the form of a <a href="#change-proposal">Change
 Proposal</a>. The process returns to <a href="#basic-step-1">step
 1</a>. Working Group Decisions must be applied within one calendar
-month of the bug being reopened. If for any reason a decision cannot
-be applied within the required time frame, the relevant spec's Editor
+week of the bug being reopened. If for any reason a decision cannot
+be applied within the required time frame, the relevant spec's Editors
 must notify the Chairs and ask for an extension.</dd>
 </dl>
 
@@ -649,20 +649,14 @@
 
 <dt id="lc-review-step-3">3. Review Period Ends</dt>
 <dd>
-<p>The end of the review period is the cutoff for bugs to be considered
+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.</p>
-
-<p>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.</p>
-
+for a future version of HTML.
 </dd>
 
 <dt id="lc-review-step-4">4. Editors Complete Initial Responses</dt>
@@ -749,7 +743,28 @@
 
 <dl>
 
-<dt id="lc2-rtc">1. Review then Commit</dt>
+<dt id="lc2-require-bugs">1. Require bugs for every change</dt>
+<dd>
+<p>Starting with second and later Last Calls, the rate of change
+should slow significantly. At this point, we require 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>
+</dd>
+
+<dt id="lc2-change-scope">2. Limit scope of bugs to changes</dt>
+<dd>
+<p>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.</p>
+<p>All bugs entered outside of this scope are to be reassigned to components
+set up for "HTML.next" activities.</p>
+<p>In rare cases, editors may select individual bugs, ensure that there is a
+proposed change, and submit such for approval to the Working Group.
+</p>
+</dd>
+
+<dt id="lc2-rtc">3. Review then Commit</dt>
 <dd>
 <p>
 Whereas the <a href="#enhanced">Enhanced Change Control</a> process merely
@@ -786,6 +801,8 @@
 process.
 </p>
 
+<p>
+</p>
 </dd>
 </dl>
 
@@ -872,11 +889,6 @@
 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
 through the Working Group. If any Working Group member sees a change
Received on Monday, 13 August 2012 17:06:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 August 2012 17:06:55 GMT