Skip to content

Commit

Permalink
Improve Prioritization procedure's summarize sections (#415)
Browse files Browse the repository at this point in the history
* Improve Prioritization procedure's summarize sections

* Update src/compiler/prioritization/procedure.md

Co-authored-by: apiraino <apiraino@users.noreply.github.com>

* Update src/compiler/prioritization/procedure.md

Co-authored-by: apiraino <apiraino@users.noreply.github.com>

* Update src/compiler/prioritization/procedure.md

Co-authored-by: apiraino <apiraino@users.noreply.github.com>

Co-authored-by: apiraino <apiraino@users.noreply.github.com>
  • Loading branch information
spastorino and apiraino committed Aug 8, 2020
1 parent 5b83095 commit ff7b7d2
Showing 1 changed file with 18 additions and 7 deletions.
25 changes: 18 additions & 7 deletions src/compiler/prioritization/procedure.md
Original file line number Diff line number Diff line change
Expand Up @@ -142,9 +142,11 @@ We will have checkins from @*WG-X* and @*WG-Y*
#### Summarize stable/beta nominations

- Add them to the agenda explaining:
- Why was it nominated
- Who the author of the PR is
- Who the assignee is
- Add important details
- Which issue fixes, it is a regression? what's the priority?
- Why was it nominated
- Add other important details

Note: triagebot automatically creates a topic and notify @*WG-prioritization* members requesting addition to the agenda.

Expand All @@ -157,8 +159,10 @@ Try to follow the [General issues review process](#general-issues-review-process
We should:

- Add them to the agenda explaining:
- What are they waiting for
- Add important details
- Who the author of the PR is
- Who the assignee is
- What is the issue waiting for
- Add other important details
- Explicitly nominate any issue that can be *quickly* resolved in a triage meeting.

Note: triagebot automatically creates a topic and notify @*WG-prioritization* members requesting addition to the agenda.
Expand All @@ -171,7 +175,14 @@ We should:

- [Notify the appropriate groups](https://rustc-dev-guide.rust-lang.org/notification-groups/about.html)
- Push them forward, if possible
- Assign if possible; if the issue remains unassigned, it should be added to the agenda so we can assign it during the meeting
- Assign if possible

- Add `P-critical`s and unassigned `P-high`s to the agenda explaining:
- If it's assigned or not and to whom
- Does it needs MCVE and/or bisection?
- Are there identified culprits?
- Do already have a PR open that fixes the issue?
- Add other important details

Note: triagebot automatically creates a topic and notify @*WG-prioritization* members requesting addition to the agenda.

Expand All @@ -186,10 +197,10 @@ We should:
- Check if these issues were already discussed and in that case remove `I-nominated` label
- Check if each issue is worth being discussed
- Add them to the agenda explaining:
- Why was it nominated
- Who the assignee is
- Is this an issue or a PR: if an issue, does it have a PR that fixes it?
- Add important details
- Why was it nominated
- Add other important details

Note: triagebot automatically creates a topic and notify @*WG-prioritization* members requesting addition to the agenda.

Expand Down

0 comments on commit ff7b7d2

Please sign in to comment.