On Friday, February 10th, the Rust Compiler team had a planning meeting for the February 2023 steering cycle.
T-compiler June Steering Schedule
| Date | Meeting Id | Meeting Topic |
|---|---|---|
| 2023-02-17 | compiler-team#589 | Dealing with PR review latency |
| 2023-02-24 | compiler-team#583 | Scope and goals of rust-lang/rust optimizations |
| 2023-03-03 | compiler-team#590 | P-high review for 2023 Q1 |
| 2023-03-10 | none | (planning for March cycle) |
Details
Every fourth Friday, the Rust compiler team decides how it is going to use its scheduled steering and design meeting time over the next three Fridays.
On Friday, 17 February, we will discuss ways to improve our Pull Request review latency. Jack Huey, apiraino, and oli-obk will work on a document to drive the meeting, collecting ideas on how to attack the problem.
On Friday, 24 February, we will discuss our philosophy about code optimizations that are implemented in the rust-lang/rust repository (as opposed to optimizations that are implemented in LLVM itself, which is where the bulk of our optimization logic currently resides). Jak{e,ob} Degen will author the document driving this meeting.
On Friday, 3 March, we will do a quarterly review of the open P-high issues. pnkfelix will do some ahead of time work in zulip triaging some of the issues, and potentially prepare a meeting document summarizing the remainder, to maximize the quality of our synchronous in-meeting time.
On Friday, 10 March, we will hold our planning meeting for the next steering cycle in March and April.
Each meeting will run from 2pm to 3pm GMT, and will take place on the T-compiler/meetings zulip stream.