-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRD may be followed by a Proposed Recommendation #450
Comments
I'm a little unsure. On the one hand, you're right, CRD->PR is possible in this case. On the other hand, it seems to me that the current text is clearer about the general intent, by naming what kind of update we're talking about, and it just so happens that we have an exception that allows you to skip CRS and go straight to PR if you've only made editorial changes. Should we go for clarity of intent, or for precision? Or should we find yet another wording that gives us both? While we're on that, I'm not sure that "subsquent update" is quite the right word anyway. A new CR(S) would be an update, but is PR really an update? |
|
well, PR is an update since it has a new date at the minimum. Spelling it out while we're trying to make the SOTD the SOTD shorter backward to me. |
@plehegar I mean, I'd be OK with dropping the entire “that the Working Group intends to include in a subsequent Candidate Recommendation Snapshot” phrase. But a CRD is also an “update” so the phrase is a bit nonsensical if we just replace “Candidate Recommendation Snapshot” with “update” here. |
Proposed wording: “A Candidate Recommendation Draft is published to solicit review of intended changes from the previous Candidate Recommendation Snapshot.” |
By focusing on what the changes in a CDR are from rather than what they're aimed at, we can both make the sentence simpler and avoid making undesired implications about the impossibility to transition from CRD to PR. This addresses w3c#450
The Revising W3C Process CG just discussed The full IRC log of that discussion<plh> Topic: #873<plh> Github: https://github.com//issues/450 <plh> Florian: it seems it's possible to move from CRD to PR if you don't make substantive changes. but the definition of CRD claims that it was only to prepare a CRS <plh> .... the PR makes things clearer <plh> Plh: +1 <plh> Resolved: Let's merge #873 |
By focusing on what the changes in a CDR are from rather than what they're aimed at, we can both make the sentence simpler and avoid making undesired implications about the impossibility to transition from CRD to PR. This addresses #450 Co-authored-by: Dominique Hazael-Massieux <dom@w3.org>
[[
A Candidate Recommendation Draft is published on the W3C’s Technical Reports page [TR] to integrate changes from the previous Candidate Recommendation Snapshot that the Working Group intends to include in a subsequent Candidate Recommendation Snapshot.
]]
https://www.w3.org/2020/Process-20200915/#candidate-recommendation-draft
However, one can go directly from CRD to Proposed Recommendation if no substantive changes were made since the most recent snapshot. So, it's not necessirely included in a subsequent CRS.
How about:
[[
A Candidate Recommendation Draft is published on the W3C’s Technical Reports page [TR] to integrate changes from the previous Candidate Recommendation Snapshot that the Working Group intends to include in a subsequent update.
]]
cc @dontcallmedom
The text was updated successfully, but these errors were encountered: