W3C home > Mailing lists > Public > public-html@w3.org > March 2010

Re: creating issues for non-published documents?

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 30 Mar 2010 11:04:03 -0700
Cc: HTMLWG WG <public-html@w3.org>
Message-id: <9A40020F-7848-4FD0-B389-1FE397464C4B@apple.com>
To: Shelley Powers <shelley.just@gmail.com>

On Mar 30, 2010, at 10:52 AM, Shelley Powers wrote:

> I noticed a couple of bugs recently that were filed against Steve
> Faulkner's alt techniques document, such as [1]. Now, they're
> resulting in issues.
> Question: how can we raise something as an issue when the bug is filed
> against a document that's not even published by this group, yet?
> This seems really screwy. For instance, what would the issue block?
> Not the HTML5 spec, would it?

Each spec is blocked only by issues that apply to that spec.

In the case of specs that have not yet been published as FPWD, it's  
not totally clear how to apply the bug process and the escalation  
process. My own inclination is that if an editor of a pre-FPWD  
document is willing to follow the bug process, then we should also let  
people raise issues, but the Chairs will probably not advance these  
issues through the formal process so long as the underlying document  
remains unpublished. However, I have not checked this thinking with my  
fellow co-Chairs, so take this as only a preliminary opinion.

Received on Tuesday, 30 March 2010 18:04:37 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:14 UTC