Weekly meeting

The agenda of this meeting is filled by the Prioritization WG. There's this document where the procedure followed by Prioritization WG is explained.

Day of the meeting

• Hi @*T-compiler/meeting*, triage meeting will be starting in ~ X hours and Y minutes
• [Check out the meeting agenda](link_to_hackmd_agenda)
• Hi @*T-compiler/meeting*! Add a :wave: emoji to show you're here :)
• we will start off with 5 minutes for ...
• ## Announcements
  • Copy announcements from Agenda
  • Team Members can also chime in with announcements. (Let discussion proceed, but try to move things along before the meeting hits the 10 minute mark.)
• Next ... [Beta nominations](https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=label%3Abeta-nominated+label%3AT-compiler)
  • List them from agenda onto Zulip
  • Tag issue as beta-accepted or remove beta-nominated (or, on rare occasions, put aside for discussion tomorrow/next week)
• Next ... [Stable nominations](https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=label%3Astable-nominated+label%3AT-compiler+)
  • List them from agenda onto Zulip
  • Tag issue as stable-accepted or remove stable-nominated
• Next ... [PR’s S-waiting-on-team](https://github.com/rust-lang/rust/pulls?utf8=%E2%9C%93&q=is%3Aopen+label%3AS-waiting-on-team+label%3AT-compiler+)
  • List them from agenda onto Zulip
  • Decide with T-compiler what to do with those
• Next ... Issues of Note
  • Copy issues of note from Agenda
    • Check if there are P-high regressions unassigned, if so assign
• Next ... [Nominated Issues](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AI-nominated+label%3AT-compiler)
  • List them from the agenda onto Zulip
  • Decide with T-compiler what to do with those
• Next ... Working Groups check-ins
  • Ask leads to share progress