W3C home > Mailing lists > Public > public-w3process@w3.org > December 2013

w3process-ISSUE-76 (CR changelogs): Requirement to document changes between CR publications [Document life cycle (ch 7)]

From: Revising W3C Process Community Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 12 Dec 2013 10:35:32 +0000
Message-Id: <E1Vr3cC-0007yS-W4@stuart.w3.org>
To: public-w3process@w3.org
w3process-ISSUE-76 (CR changelogs): Requirement to document changes between CR publications [Document life cycle (ch 7)]

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

Raised by: Ian Jacobs
On product: Document life cycle (ch 7)

Ian wrote in 

  In this section, one bullet is:
 
   "If the document has previously been published as a Candidate
   Recommendation, must document the changes since the previous
   Candidate Recommendation, "
 
  It is not clear to me how this differs from the general requirement:
 
   "must provide public documentation of all substantive changes to
   the technical report since the previous publication. The community
   also appreciates public documentation of minor changes."
 
  You might have something specific in mind, but as written I can't
  determine the difference. Or if the difference is "documenting all
  changes" instead of "documenting substantive changes" then I'm not
  sure that difference is necessary to justify the specific bullet.
  If the consensus ends up being that it is necessary, then I think the
  difference from the general bullet needs to be clearer.

The difference is documenting *all* changes, vs a must for substantive and a should for other changes...

It is not clear that the difference is important enough to keep the special requirement.
Received on Thursday, 12 December 2013 10:35:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:09 UTC