This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
To avoid an endless cycle of Last Calls, we need to limit the comments that will be accepted for subsequent LCs. Thus, we should limit the scope of LC2 and later bugs to relate to items that were changed since the previous LC.
Created attachment 1114 [details] Patch to limit LC2 and subsequent scope to changes from the previous LC
(In reply to comment #1) > Created attachment 1114 [details] > Patch to limit LC2 and subsequent scope to changes from the previous LC We probably need to add an exception mechanism, this can be as simple as a CfC of the WG.
(In reply to comment #2) > > We probably need to add an exception mechanism, this can be as simple as a CfC > of the WG. Draft wording: "The Chairs can grant exceptions on a case-by-case basis in response to a request made on public-html. The Chairs will determine if the WG agrees by doing a Call for Consensus on permitting the identified bug to be consider during the current Last Call."
Capturing a suggestion originally made by Paul in response to input from Tantek in the May 2012 F2F: We should proactively state in our announcement of LC2 that we intend to advance to CR after this LC.
Based on <http://dev.w3.org/html5/decision-policy/html5-2014-plan.html>, this proposal should reflect CR instead of LC2.