Re: CR exit criteria and features at risk for HTML5

On 8/16/12 1:40 PM, Maciej Stachowiak wrote:
>However, so far as I know, reaching the Recommendation maturity level 
has the following set of effects:
> (1) Signal to the broader community that work on the specification is done.
> (2) Greater willingness to cite or reference the spec, for those who consider the formal maturity level important.
> (3) Patent commitments come fully into effect; the RF license obligation technically only applies once the spec hits REC.
> (4) Some level of interoperability improvement and reality check happens, depending on the CR exit criteria and the quality of the test suite.
> (5) It becomes somewhat more cumbersome to change the document if problems are identified.

Thank you.  That's very helpful

> In general, it seems good for (1)-(3) to happen quickly. The "permissive" proposed set of CR exit criteria would make them happen faster. The tradeoff is doing less of (4), and therefore perhaps suffering the consequences of (5) more keenly.

Yep.  I think in this case, I'd argue for moving quickly and moving on, 
while working on a test suite to do #4 completely independent of the REC 


Received on Thursday, 16 August 2012 18:51:08 UTC