final_review.tt 1.3 KB

1234567891011121314151617181920212223242526
  1. ## Announcements
  2. - Check the compiler calendar to see if there's an outstanding event to announce.
  3. ## Nominate issues
  4. Check how packed the agenda looks like and if there's room for more, consider the following ...
  5. - [All Stable-to-beta regressions](https://github.com/rust-lang/rust/labels/regression-from-stable-to-beta)
  6. - Check if there are relevant issues that are worth raising awareness.
  7. - Assign if possible; if it remains unassigned, add it to agenda so we can assign during the meeting.
  8. - [All Stable-to-nightly regressions](https://github.com/rust-lang/rust/labels/regression-from-stable-to-nightly)
  9. - Check if there are relevant issues that are worth raising awareness.
  10. - Assign if possible; if it remains unassigned, add it to agenda so we can assign during the meeting.
  11. - [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+)
  12. - [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)
  13. ## Toolstate
  14. - Check [toolstate](https://rust-lang-nursery.github.io/rust-toolstate/) for outstanding tool breakage.
  15. - Notify teams in the corresponding channels
  16. ## Performance regressions
  17. - Check [perf regressions](http://perf.rust-lang.org/index.html).
  18. - Notify involved actors.