-
Notifications
You must be signed in to change notification settings - Fork 79
add merge and publication policy #2363
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
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -193,7 +193,7 @@ If this happens, a new "Call for Review" should be launched after the first one. | |||||||||
| - Be aware that this is last chance to object to the rule, on everything from spelling and grammar to accessibility requirements mapping and use of definitions. | ||||||||||
| - Keep up to date on Calls for Review using this list: https://github.com/act-rules/act-rules.github.io/issues/461 | ||||||||||
|
|
||||||||||
| ## Done | ||||||||||
| ## Publication | ||||||||||
|
|
||||||||||
| Published rules | ||||||||||
|
|
||||||||||
|
|
@@ -204,6 +204,17 @@ Published rules | |||||||||
| - went through Call for Review (if applicable), and change requests have been resolved | ||||||||||
| - been merged and published as a proposed rule in the WAI website at https://www.w3.org/WAI/standards-guidelines/act/rules/ (ACT Rules on the WAI website are generally updated every Tuesday) | ||||||||||
|
|
||||||||||
| ### Merge and publication policy | ||||||||||
|
|
||||||||||
| To give implementors of ACT Rules time to update implementation data, pull requests cannot be merged on Friday, Saturday, or Sunday. Those three days are reserved for implementors to update their implementation data (automated or otherwise). The publication cycle works as follows: | ||||||||||
|
|
||||||||||
| 1. Pull requests in [act-rules/act-rules.github.io][] can be merged Monday through Thursday. | ||||||||||
| 2. Implementors have Friday, Saturday or Sunday to update implementation data. | ||||||||||
| 3. Monday morning a publication candidate is created as a pull request in [w3c/wcag-act-rules][], for review by WAI staff. | ||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||
| 4. Somewhere that week, usually Monday or Tuesday, the publication candidate is approved and published to the WAI website. | ||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
We strive to (and usually) approve and publish during the week, but sometime it is delayed. |
||||||||||
|
|
||||||||||
| For substantial changes, implementors may request a publication be skipped to allow extra time for implementation. This should be done on the publication candidate pull request. It is up to discretion of W3C staff to decide whether the publication is skipped. | ||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Minor. @daniel-montalvo please note that I've included your suggested changes in my suggestion. |
||||||||||
|
|
||||||||||
| ## Rejected | ||||||||||
|
|
||||||||||
| Rules that have been rejected due to different reasons. | ||||||||||
|
|
@@ -212,3 +223,6 @@ Rules that have been rejected due to different reasons. | |||||||||
|
|
||||||||||
| - Initial rules don't get the backing they need to move on through the process. | ||||||||||
| - When a rule at any stage is dropped because it lacks backing in the Community Group, e.g. because it is not considered feasible, or is subject to disagreement on whether the rule is actually testing for something that can improve accessibility. | ||||||||||
|
|
||||||||||
| [w3c/wcag-act-rules]: https://github.com/w3c/wcag-act-rules | ||||||||||
| [act-rules/act-rules.github.io]: https://github.com/act-rules/act-rules.github.io/ | ||||||||||
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.
What happens if something gets merged on Monday, or on Tuesday, right before the WAI website update goes live? As I said yesterday, I think we should restrict the updates coming from the act-rules.github.io repo to a specific date and time during the week, which could be Thursdays after the meeting when hopefully all has been merged.