This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16676 - Limit scope of LC2 bugs to relate to items that were changed since LC1
Summary: Limit scope of LC2 bugs to relate to items that were changed since LC1
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: working group Decision Policy (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Maciej Stachowiak
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-10 03:14 UTC by Maciej Stachowiak
Modified: 2012-09-25 16:15 UTC (History)
4 users (show)

See Also:

Attachments
Patch to limit LC2 and subsequent scope to changes from the previous LC (1.52 KB, patch)
2012-04-10 04:17 UTC, Maciej Stachowiak 		Details

Description Maciej Stachowiak 2012-04-10 03:14:42 UTC 
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.
Comment 1 Maciej Stachowiak 2012-04-10 04:17:06 UTC 
Created attachment 1114 [details]
Patch to limit LC2 and subsequent scope to changes from the previous LC
Comment 2 Sam Ruby 2012-04-10 16:06:51 UTC 
(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.
Comment 3 Sam Ruby 2012-04-16 11:26:48 UTC 
(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."
Comment 4 Sam Ruby 2012-05-03 17:26:06 UTC 
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.
Comment 5 Sam Ruby 2012-09-25 16:15:50 UTC 
Based on <http://dev.w3.org/html5/decision-policy/html5-2014-plan.html>, this proposal should reflect CR instead of LC2.