-
Notifications
You must be signed in to change notification settings - Fork 63
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
[template] Avoid mentioning PR directly #578
base: gh-pages
Are you sure you want to change the base?
Conversation
There are proposed changes in the Process about simplifying the REC track that if adopted would result in Proposed Recommendation being retired as a maturity stage. The requirements to exit CR would remain the same though. This rephrasing recasts the criteria expect in order to enter PR in terms of exiting CR instead. This is strictly equivalent, but avoids mentioning PR by name, making this language more forward compatible with this potential upcoming Process change.
<p><span class='todo'>Remove this clause if the Group does not intend to move to REC:</span> In order to advance to | ||
<a href="https://www.w3.org/policies/process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have | ||
<p><span class='todo'>Remove this clause if the Group does not intend to move to REC:</span> In order to advance beyond | ||
<a href="https://www.w3.org/policies/process/#RecsCR" title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is expected to have |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your PR didn't change this, but it seems unnecessary to have a title
on the link that just repeats the content of the link.
<a href="https://www.w3.org/policies/process/#RecsCR" title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is expected to have | |
<a href="https://www.w3.org/policies/process/#RecsCR">Candidate Recommendation</a>, each normative specification is expected to have |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM including suggested change from @jyasskin
There are proposed changes in the Process about simplifying the REC track that if adopted would result in Proposed Recommendation being retired as a maturity stage. The requirements to exit CR would remain the same though.
This rephrasing recasts the criteria expect in order to enter PR in terms of exiting CR instead. This is strictly equivalent, but avoids mentioning PR by name, making this language more forward compatible with this potential upcoming Process change.