This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The Chairs should define a procedure for entering Last Call and put it in the Decision Policy. Here are our tentative thoughts: 1) Editor should advise the chairs privately (or say on list?) when he/she feels a draft is ready for Last Call 2) If Chairs agree, we advise people that if they plan to object to Last Call, they should make sure their concerns are at least recorded as a bug by then, because we would rather not see new input on the Last Call resolution itself. We will define a pre-LC review period with a cutoff date by which people should get their concerns at least in bugzilla. 3) We do not go to Last Call until all bugs filed by the cutoff are in a terminal state (which also implies resolving any issues escalated from those bugs) 4) If the Chairs think that proceeding to Last Call is advisable given the pre-LC review feedback, and how any bugs and issues resulting from it got resolved, then we do a simple one-week Call for Consensus
Strawman resolution: document the process described in the initial description.
Timeline to last call: http://lists.w3.org/Archives/Public/public-html/2010Sep/0074.html
The procedure for Last Call and Pre-Last Call review is defined here: http://dev.w3.org/cvsweb/html5/decision-policy/decision-policy-v2.html.diff?r1=1.16&r2=1.17&f=h The resolution was based on the established practice of timelines.