Bug 16647 - CR exit criteria should explicitly list features "at risk"
CR exit criteria should explicitly list features "at risk"
Status: RESOLVED FIXED
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL
unspecified
All All
: P2 normal
: ---
Assigned To: Cameron McCormack
public-webapps-bugzilla
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-06 08:48 UTC by Ms2ger
Modified: 2012-04-08 23:33 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ms2ger 2012-04-06 08:48:14 UTC
The spec states: [1]

> Any features of Web IDL that are not in use by any Web specification
> by the time the test suite is otherwise complete will be considered
> at risk and will be dropped. 

while the Process document explains: [2]

> In the Call for Implementations, the Working Group MAY identify
> specific features of the technical report as being "features at
> risk." General statements such as "We plan to remove any
> unimplemented feature" are not acceptable; the Working Group MUST
> precisely identify any features at risk. Thus, in response to a Call
> for Implementations, reviewers can indicate whether they would
> register a Formal Objection to the decision to remove the identified
> features.

[1] http://dev.w3.org/2006/webapi/WebIDL/#cr-exit
[2] http://www.w3.org/2005/10/Process-20051014/tr.html#cfi
Comment 1 Cameron McCormack 2012-04-08 23:33:32 UTC
Thanks, I wasn't aware of that restriction.  I've gone back to enumerating some features that are currently or might be unused.