- From: <bugzilla@jessica.w3.org>
- Date: Mon, 19 Apr 2010 20:32:58 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9554 Summary: Define procedure for entering Last Call Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: working group Decision Policy AssignedTo: dave.null@w3.org ReportedBy: mjs@apple.com QAContact: public-html-bugzilla@w3.org CC: mjs@apple.com, Paul.Cotton@microsoft.com, rubys@intertwingly.net, mike@w3.org 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 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 19 April 2010 20:33:12 UTC