--- tags: prioritization, rustc --- # Prioritization WG - Check-ins ## Current ## 2020-09-23 - We published last week a [Call for new contributors](https://blog.rust-lang.org/2020/09/14/wg-prio-call-for-contributors.html). The answer was above our expectations, to this day we have received 13 new applications and we are therefore encouraging new volunteers showing up to also join the [Cleanup ICE-breaker and bisect group](https://rustc-dev-guide.rust-lang.org/notification-groups/cleanup-crew.html). ## 2020-08-06 - We have now a [repo for the working group](https://github.com/rust-lang/compiler-team-prioritization/) and we are mainly handling our todo list as issues there. - Our procedure automation cli is "complete" and outputs the agenda but we still need to integrate it with the Zulip bot. - We've [documented our procedure](https://forge.rust-lang.org/compiler/prioritization/procedure.html) with a lot of details on Rust Forge. - We have added Pre-FCP and FCP information to the announcements. - There's a list of things we need to tweak [in our issue tracker](https://github.com/rust-lang/compiler-team-prioritization/issues?q=is%3Aopen+is%3Aissue), help is appreciated :) ## 2020-06-18 - We are now executing our process fully async and have bi-weekly planning/steering meetings to think about things to improve. - We've prioritized all `I-unsound 💥` issues for `T-compiler` and `libs-impl` - From now on new issues tagged with `I-unsound 💥` will automatically add `I-prioritize` and then request prioritization to the wg. - There are not unprioritized regressions anymore :tada: - We've prioritized all `regression-from-stable-to-stable` issues for `T-compiler` and `libs-impl` - From now on new issues tagged with `regression-from-stable-to-stable` will automatically add `I-prioritize` and then request prioritization to the wg. - Same happens for `regression-from-stable-to-beta` and `regression-from-stable-to-nightly` - We are in the process of automating most of our procedure ## 2020-04-30 This is the first checkin from WG Prioritization. - [The group is formally formed](https://rust-lang.github.io/compiler-team/working-groups/prioritization/) - Main goal is to triaging bugs, mainly deciding if bugs are critical (potential release blockers) or not. - Route bugs to folks who can fix them. - Build the agenda for these meetings. - Among other things :) - We have [some plans](https://hackmd.io/P3yvagSSS7yAI2QxhLfPtQ?view) and [procedures](https://hackmd.io/pHb6eTZ2Sjy6XZmwXZHIBA?view) documented. - We've created I-prioritize and splitted the meaning of it with I-nominated for easier request for prioritization. - We've created P-critical and defined the [different priority levels](https://hackmd.io/7NRRbq62TnaezW7-n15cDw) this is still WIP. - We're trying to have all this process async - When someone tags `I-prioritize` a Zulip topic is automatically created requesting for prioritization of the issue in question so we can prioritize async. - @rustbot prioritize works too for non-members - We should do the same for beta/stable backports, I-nominated, S-waiting-on-team - We're also trying to automate with commands our meetings and this one in particular.