W3C home > Mailing lists > Public > public-html-admin@w3.org > January 2013

Re: Bugs organisation

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 14 Jan 2013 16:54:20 +0000
Message-ID: <CA+ri+V=HrU+AT3S8r+xTv=2aLcJ=6MZ=YXEidkBhtMggqY9Udw@mail.gmail.com>
To: Robin Berjon <robin@w3.org>
Cc: public-html-admin@w3.org
sounds like a good plan, thanks!

On 14 January 2013 16:51, Robin Berjon <robin@w3.org> wrote:

> Hi all,
>
> we currently have a bunch of different places with bugs against the HTML
> spec.
>
> Under product HTML WG, by component:
> CR HTML5 spec           8 bugs
> HTML5 spec              127 bugs
> LC1 HTML5 spec          2 bugs
> maincontent element     4 bugs
> pre-LC1 HTML5 spec      3 bugs
>
> Under product HTML.next, by component:
> default                 115 bugs
>
> That's a bit of a mess. I'd like to propose the following organisation:
>
>  HTML WG/CR HTML5 spec: all the bugs that we plan to fix inside of the CR
> (typically, typos and various kinds of must-have fixes).
>
>  HTML WG/HTML 5.1: all the bugs that we plan to fix in 5.1.
>
>  HTML.next/default: anything that we might consider for 5.2, but not now
> (at this stage, I don't expect there to be anything in there).
>
> That involves going through the above list of 259 bugs and moving them. I
> don't want to presume that existing bugs are well-categorised, except for
> HTML.next bugs which I think can be mass-moved to 5.1.
>
> Any thoughts? If no one objects, I'll go ahead and do that.
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Monday, 14 January 2013 16:55:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 January 2013 16:55:30 GMT