ISSUE-87: How to ensure you got wide review to enter CR

coming to CR

How to ensure you got wide review to enter CR

State:
CLOSED
Product:
Document life cycle (pre 2014 chapter 7, now chapter 6)
Raised by:
Charles 'chaals' (McCathie) Nevile
Opened on:
2014-02-14
Description:
I am proposing a change to the wording in the document, based on a proposal by Ian in http://lists.w3.org/Archives/Public/public-w3process/2014Feb/0015.html:

from

A recommended practice is making a specific announcement to other W3C Working Groups as well as the general public, especially the sub-communities thereof that are affected by this specification, that a group proposes to enter Candidate Recommendation in e.g. approximately four weeks.

to

Working Groups should announce to other W3C Working Groups as well as the general public, especially those affected by this specification, a proposal to enter Candidate Recommendation in e.g. approximately four weeks

This change is purely editorial - "recommended" and "should" are equivalent in RFC2119 already - but since the wording there was agreed in a Resolution I wanted to raise an explicit issue that people could track if they wanted to.
Related Actions Items:
No related actions
Related emails:
  1. Re: w3process-ISSUE-87 (coming to CR): How to ensure you got wide review to enter CR [Document life cycle (ch 7)] (from szilles@adobe.com on 2014-02-15)
  2. w3process-ISSUE-87 (coming to CR): How to ensure you got wide review to enter CR [Document life cycle (ch 7)] (from sysbot+tracker@w3.org on 2014-02-14)

Related notes:

No additional notes.

Display change log ATOM feed


David Singer <singer@apple.com>, Chair, Dominique Hazaƫl-Massieux <dom@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 87.html,v 1.1 2020/03/09 13:50:20 carcone Exp $