W3C home > Mailing lists > Public > public-w3process@w3.org > February 2014

w3process-ISSUE-87 (coming to CR): How to ensure you got wide review to enter CR [Document life cycle (ch 7)]

From: Revising W3C Process Community Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 14 Feb 2014 20:29:52 +0000
Message-Id: <E1WEPOS-0004xG-BT@stuart.w3.org>
To: public-w3process@w3.org
w3process-ISSUE-87 (coming to CR): How to ensure you got wide review to enter CR [Document life cycle (ch 7)]

http://www.w3.org/community/w3process/track/issues/87

Raised by: Charles McCathie Nevile
On product: Document life cycle (ch 7)

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.
Received on Friday, 14 February 2014 20:29:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:17 UTC