ACTION-44: Write updated wording for CR drafts exit criteria

Write updated wording for CR drafts exit criteria

State:
closed
Person:
Peter Linss
Due on:
April 19, 2008
Created on:
April 5, 2008
Related emails:
  1. RE: [css3-flexbox] open issues in spec (from alexmog@microsoft.com on 2012-02-28)
  2. Re: [css3-flexbox] open issues in spec (from fantasai.lists@inkedblade.net on 2012-02-23)
  3. [css3-flexbox] open issues in spec (from alexmog@microsoft.com on 2012-02-23)
  4. [CSSWG] Minutes and Resolutions Seattle F2F 2011-07-26 PM: Compositing, Filters, Animations, Transforms, SVG Params (from fantasai.lists@inkedblade.net on 2011-08-05)
  5. Re: [css3-color] Remarks on status section (from peter.linss@hp.com on 2008-06-25)
  6. Re: [css3-color] Remarks on status section (from fantasai@inkedblade.net on 2008-06-25)
  7. Re: [css3-color] Remarks on status section (from peter.linss@hp.com on 2008-06-25)
  8. Re: New CR exit criteria (from annevk@opera.com on 2008-04-05)
  9. Re: New CR exit criteria (from bert@w3.org on 2008-04-05)

Related notes:

http://www.w3.org/2008/03/26-css-irc.html#T23-45-11 (ftf San Diego)

Bert Bos, 5 Apr 2008, 10:53:03

There must be at least two independent, interoperable implementations of each feature. Each feature may be implemented by a different set of products, there is no requirement that all features be implemented by a single product. For the purposes of this criterion, we define the following terms:

independent – each implementation must be developed by a different party and cannot share, reuse, or derive from code used by another qualifying implementation. Sections of code that have no bearing on the implementation of this specification are exempt from this requirement.

interoperable - passing the respective test case(s) in the official CSS test suite, or, if the implementation is not a Web browser, an equivalent test. Every relevant test in the test suite should have an equivalent test created if such a user agent (UA) is to be used to claim interoperability. In addition if such a UA is to be used to claim interoperability, then there must one or more additional UAs which can also pass those equivalent tests in the same way for the purpose of interoperability. The equivalent tests must be made publicly available for the purposes of peer review.

implementation - a user agent which:
1) implements the specification.
2) is available to the general public. The implementation may be a shipping product or other publicly available version (i.e. beta version, preview release, or "nightly build"). Non-shipping product releases must have implemented the feature(s) for a period of at least one month in order to demonstrate stability.
3) is not experimental (i.e. a version specifically designed to pass the test suite and is not intended for normal usage going forward).

Peter Linss, 6 May 2008, 21:25:58

WG resolved to accept wording 28 May 08

Peter Linss, 4 Jun 2008, 16:47:27

Changelog:

Created action 'Write updated wording for CR drafts exit criteria' assigned to Peter Linss, due 2008-04-19

5 Apr 2008, 10:51:53

Status changed to 'pending review'

6 May 2008, 21:25:58

Status changed to 'closed'

4 Jun 2008, 16:47:27


Peter Linss <peter.linss@hp.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, Chairs, Chris Lilley <chris@w3.org>, Bert Bos <bert@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $