W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: How to track issues that block PR but not Last Call (was Re: ISSUE-53: mediatypereg - suggest closing on 2009-09-03)

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 23 Sep 2009 23:40:03 -0700
Cc: Sam Ruby <rubys@intertwingly.net>, Ian Hickson <ian@hixie.ch>, Julian Reschke <julian.reschke@gmx.de>, Henri Sivonen <hsivonen@iki.fi>, "public-html@w3.org WG" <public-html@w3.org>
Message-id: <DF51C97B-E025-4CFF-B5A0-1759EA9B023B@apple.com>
To: Dan Connolly <connolly@w3.org>

On Aug 24, 2009, at 7:35 AM, Dan Connolly wrote:

> On Sat, 2009-08-22 at 21:14 -0700, Maciej Stachowiak wrote:
> [...]
>> I'd like to ask the Chairs and Team Contacts for a their input on how
>> to track issues that should not block Last Call, but should block PR.
>> The need for such a status has become clear not only with this issue,
>> but also with the issue of "about" registration.
>>
>> Dan Connolly proposed that issues marked as "Pending Review" can be
>> treated as blocking PR but not LC. I don't think that works, given  
>> our
>> current definition of Pending Review, which is that consensus has not
>> yet been assessed (which might well indicate the issue blocks Last
>> Call).
>>
>> My proposal, create a new product in the tracker, "HTML5 spec PR".
>> Issues that block PR but not Last Call would be moved to this new
>> product.
>
> That works for me.

I created a component named "HTML5 spec - PR blockers" and moved  
ISSUE-53 there.

Regards,
Maciej
Received on Thursday, 24 September 2009 06:40:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:48 GMT