Wednesday, 26 November 2008

Mr Frosties HTML5 feature freeze

Like climbing an Icy Pole
There were a couple other new features added this week, which I’m also kind of mystified by. I did ask on IRC, but I don’t think Ian’s response was very direct. It seems the only requirement to qualify for addition after the freeze is that Ian must be able to frame the new a feature as a response to at least one email sent over a two year period.
Robert sayre - http://blog.mozilla.com/rob-sayre/2008/11/25/slurpee/

sayrer: Hixie, so, I thought there was a feature freeze? but now we have this new 401 form...
Hixie: sayrer: i said i wasn't adding anything new that hadn't already been requested as of the feature freeze (last december)
Hixie: the recent additions are from requests from 2006/2007
sayrer: that doesn't seem like a useful freeze to me
sayrer: thanks
Hixie: (or, in the case of workers, from requests from browser vendors who said that without a spec they'd just make up stuff)
Hixie: well the freeze is only intended to land us on schedule
sayrer: well, you are a browser vendor just making stuff up :)
Hixie: i mean implementors
* sayrer shrugs
hsivonen: Hixie: seems more like a suggestion freeze than a feature freeze :-)
Hixie: yeah, that'd be a better term
Hixie: i don't recall exactly how i phrased it

read more



the W3C version of this timetable is ludicrous.
Hixie follow me not the W3C - Pink unisex vest from the WHAT Working Gear range


As far as the timetable goes, I am confident that we will make the 2009 (LC) date and the 2012 (CR) date
...
I agree that the W3C version of this timetable is ludicrous.
Ian hickson

...
More exactly, the definitions behind hixie:LC and hixie:CR are not the same than w3c:LC and w3c:CR.
Karl Dubost
read more

0 comments: