|
3 | 3 | ## Issues
|
4 | 4 | 1. An issue is made on the ARIA repository
|
5 | 5 | 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. |
7 | 7 | - 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. |
10 | 10 | 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.
|
11 | 11 |
|
12 | 12 | ## Pull Requests
|
13 | 13 |
|
14 | 14 | Newly opened PRs are "triaged" at the next ARIA meeting. At triage, it is decide:
|
15 | 15 | - 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. |
17 | 23 |
|
18 | 24 | ### Normative Changes
|
19 | 25 |
|
|
0 commit comments