Fwd: Last Call timeline

I'm forwarding information on the Last Call timeline from Paul.

- Judy


>From: Paul Cotton <Paul.Cotton@microsoft.com>
>To: "public-html@w3.org" <public-html@w3.org>
>CC: "Sam Ruby (rubys@intertwingly.net)" <rubys@intertwingly.net>, "Maciej
>  Stachowiak (mjs@apple.com)" <mjs@apple.com>, "Philippe Le Hegaret
>  (plh@w3.org)" <plh@w3.org>, "Michael(tm) Smith (mike@w3.org)" <mike@w3.org>
>Date: Sun, 15 May 2011 18:06:29 +0000
>Subject: Last Call timeline
>Archived-At: 
><http://www.w3.org/mid/E3EACD022300B94D88613639CF4E25F81A2CBE6E@TK5EX14MBXC132.redmond.corp.microsoft.com>
>
>The Chairs have been discussing with the W3C Team the need for a 
>timeline for Last Call. The W3C Team has asked us to create a 
>timeline to drive the Last Call to successful completion and we 
>agree that this is essential to successfully progress the HTML Last 
>Call Working Drafts.
>
>The key aspect of this timeline is that there will be a cutoff date 
>for bugs to be considered during Last Call; any bugs after that date 
>will instead be treated during a subsequent Last Call, possibly 
>during Candidate Recommendation or for a subsequent version of 
>HTML.  The Last Call period for the WG's Last Call Working Drafts 
>will be 10 weeks long from May 24 through Aug 2.  Any bug in the 
>system by Aug 2 (even if reopened, resolved, or escalated) will be 
>resolved during Last Call, and we will fully process any that are 
>escalated to issues.
>
>Each date in this timeline is a deadline with a consequence. If the 
>date is missed, the consequence *will* be applied. If there are any 
>issues that WG Members or reviewers feel are critical to address 
>during Last Call, then it is essential to make sure they are in the 
>bug system ASAP and that other required milestones are met.
>
>If anyone has any questions, feel free to ask here, ask the chairs 
>privately, or ask off list on www-archive@w3.org.
>
>= Timeline =
>
>- May 24, 2011 - Opening of Last Call review period - May 24-Aug 2 (10 weeks)
>- May 24, 2011 - Commence processing of open issues that exist at 
>the start of Last Call
>Consequences of missing this date: Delay in processing of open 
>issues at the start of Last Call will put subsequent dates at risk.
>
>(6 weeks)
>
>- Jul 5, 2011 - all bugs filed by the start of Last Call addressed by editors
>Consequences of missing this date: bugs still open past this date 
>can be escalated to issues immediately if the originator so chooses.
>
>(4 weeks)
>
>- Aug 2, 2011 - cutoff for bugs to be considered as Last Call feedback
>Consequence of missing this date: bugs beyond this date will NOT be 
>treated as Last Call comments. 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.
>
>(8 weeks)
>
>- Sep 27, 2010 - all bugs filed by Last Call cutoff date addressed by editors
>Consequences of missing this date: bugs still open past this date 
>can be escalated to issues immediately if the originator so chooses.
>
>(2 weeks)
>
>- Oct 11, 2010 - cutoff for escalating bugs for Last Call 
>consideration - all issues in tracker, calls for proposal issued by this date
>Consequences of missing this date: any further escalations will not 
>be treated as a Last Call comment.
>
>(4 weeks)
>
>- Nov 8, 2011 - every issue has at least one Change Proposal
>Consequences of missing this date: issues will be closed without 
>prejudice and marked POSTPONED; can be reconsidered during second LC 
>or for a later version of HTML.
>
>(4 weeks)
>
>- Dec 6, 2011 - all calls for counter-proposals complete
>Consequences of missing this date: if any issue has only one 
>proposal, we will call for consensus on that proposal.
>
>(4 weeks plus 2 weeks for end of the year holidays)
>
>- Jan 17, 2012 - all issues resolved; next step resolution presented 
>to HTML Working Group
>Consequences of missing this date: this would be solely a failure by 
>the Chairs, so we would publicly eat crow and plot a new date.
>
>(2 weeks)
>
>- Jan 31, 2012 - fixable LC objections addressed; if all goes well, 
>next step resolution carries
>Consequences of missing this date: try next step resolution again.
>
>/paulc
>for the HTML WG co-chairs
>
>Paul Cotton, Microsoft Canada
>17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>Tel: (425) 705-9596 Fax: (425) 936-7329

Received on Monday, 16 May 2011 16:36:36 UTC