final_review.tt 1.4 KB

123456789101112131415161718192021222324252627
  1. ## Announcements
  2. - Check the compiler calendar to see if there's an outstanding event to announce.
  3. - Add those to the agenda properly linking issues and documents.
  4. ## Nominate issues
  5. Check how packed the agenda looks like and if there's room for more, consider the following ...
  6. - [All Stable-to-beta regressions](https://github.com/rust-lang/rust/labels/regression-from-stable-to-beta)
  7. - Check if there are relevant issues that are worth raising awareness.
  8. - Assign if possible; if it remains unassigned, add it to agenda so we can assign during the meeting.
  9. - [All Stable-to-nightly regressions](https://github.com/rust-lang/rust/labels/regression-from-stable-to-nightly)
  10. - Check if there are relevant issues that are worth raising awareness.
  11. - Assign if possible; if it remains unassigned, add it to agenda so we can assign during the meeting.
  12. - [P-high issues](https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3AT-compiler+label%3AP-high+)
  13. - [unassigned](https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3AT-compiler+label%3AP-high+no%3Aassignee)
  14. ## Toolstate
  15. - Check [toolstate](https://rust-lang-nursery.github.io/rust-toolstate/) for outstanding tool breakage.
  16. - Notify teams in the corresponding channels
  17. ## Performance regressions
  18. - Check [perf regressions](http://perf.rust-lang.org/index.html).
  19. - Notify involved actors.