- From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 25 Sep 2012 16:59:02 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/decision-policy In directory hutz:/tmp/cvs-serv8276 Modified Files: decision-policy-v3.html Log Message: Tweaks for plan2014: * s/lc2/cr/ * s/72hr/1 week/ in RTC Index: decision-policy-v3.html =================================================================== RCS file: /sources/public/html5/decision-policy/decision-policy-v3.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- decision-policy-v3.html 25 Sep 2012 16:03:41 -0000 1.5 +++ decision-policy-v3.html 25 Sep 2012 16:59:00 -0000 1.6 @@ -65,7 +65,7 @@ <li><a href="#cp-review-process">6. Change Proposal Review Process</a> - The process by which Chairs review Change Proposals.</li> <li><a href="#lc-review">7. First Last Call and Pre-Last Call Review Process</a> - The meta-process by which the Working Group drives an LC or Pre-LC Review.</li> -<li><a href="#lc2">8. Second Last Call Process Additions</h2> - additions +<li><a href="#cr">8. Candidate Recommendation Process Additions</h2> - additions intended to reduce the rate of change to the document.</li> <li><a href="#reopening">9. Requests for a Decision to be Reopened Based on New Information</a> - The process by which Working Group members may ask to have a decision reopened, if they believe they have relevant new information.</li> <li><a href="#enhanced-cc">10. Enhanced Change Control</a> - The policy for enhanced change control and revert requests after specific pre-LC cutoff dates and during LC review.</li> @@ -740,14 +740,14 @@ </section> <section> -<h2 id="lc2">8. Second Last Call Process Additions</h2> +<h2 id="cr">8. Candidate Recommendation Process Additions</h2> <p>Once the first set of comments have been processed, focus turns to stabilizing the specification.</p> <dl> -<dt id="lc2-require-bugs">1. Require bugs for every change</dt> +<dt id="cr-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 @@ -755,7 +755,7 @@ 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> +<dt id="cr-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 @@ -768,7 +768,7 @@ </p> </dd> -<dt id="lc2-rtc">3. Review then Commit</dt> +<dt id="cr-rtc">3. Review then Commit</dt> <dd> <p> Whereas the <a href="#enhanced">Enhanced Change Control</a> process merely @@ -787,8 +787,8 @@ manner. </p> <p> -At least 72 hours must be provided for approvals, and additional time should -be provided should this period span a weekend or a holiday. Objections are to +At least one week must be provided for approvals, and additional time should +be provided should this period span a major holiday. Objections are to also be made on the public-html mailing list. If no objections are raised during that period, the change can go in. </p>
Received on Tuesday, 25 September 2012 16:59:03 UTC