Skip to content

Commit 05c5c5e

Browse files
authored
Editorial: add draft PR definition to documentation (#2063)
1 parent 75f7ad7 commit 05c5c5e

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

documentation/process.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,23 @@
33
## Issues
44
1. An issue is made on the ARIA repository
55
2. New issues are "triaged" at the next ARIA WG meeting. During triage, the following happens:
6-
- A release tag is added for purposes of prioritizing whether the issue is resolved in the current release of ARIA or a subsequent release.
6+
- A release label is added for purposes of prioritizing whether the issue is resolved in the current release of ARIA or a subsequent release.
77
- WG members are assigned to the issue if appropriate.
8-
- If the issue clearly needs group discussion, the "agenda" tag is added to the issue in order for the issue to be scheduled for discussion at a later meeting.
9-
3. WG members can add the "agenda" tag to any issue they feel needs more discussion in order to reach consensus.
8+
- If the issue clearly needs group discussion, the "agenda" label is added to the issue in order for the issue to be scheduled for discussion at a later meeting.
9+
3. WG members can add the "agenda" label to any issue they feel needs more discussion in order to reach consensus.
1010
4. After the issue is discussed in a meeting, a WG member should be assigned to summarize the conclusion of the discussion in the issue and open a PR with relevant changes.
1111

1212
## Pull Requests
1313

1414
Newly opened PRs are "triaged" at the next ARIA meeting. At triage, it is decide:
1515
- Who should review the PR
16-
- If the PR needs extra discussion by the whole ARIA WG, the "agenda" tag can be added.
16+
- If the PR needs extra discussion by the whole ARIA WG, the "agenda" label can be added.
17+
18+
Draft PRs are not triaged at meeting and are considered not read for review. If you want to prevent an approved PR from getting merged, add the `do not merge` label.
19+
20+
PR Labels:
21+
- `waiting for implementations`: if a normative PR has been approved but there are no implementations yet, then use this flag to indicate it can be merged when the implementations are completed.
22+
- `do not merge`: if a PR has approving reviews but there is some reason to wait for merging.
1723

1824
### Normative Changes
1925

0 commit comments

Comments
 (0)