File tree Expand file tree Collapse file tree 2 files changed +10
-10
lines changed Expand file tree Collapse file tree 2 files changed +10
-10
lines changed Original file line number Diff line number Diff line change 2
2
The compiler team host various regular meetings to keep on top of regular business necessary for
3
3
the running of the team and delivery of a high-quality compiler toolchain.
4
4
5
+ All the T-compiler meetings are held in our Zulip chat [ ` #t-compiler/meetings ` ] [ meetings_channel ] ,
6
+ in text-mode only.
7
+
5
8
## Triage Meeting
6
- The weekly triage meeting takes place on Zulip: considering any backports, reviewing
7
- performance triage reports and discussing nominated issues. Triage meetings are held in the
8
- [ ` #t-compiler/meetings ` ] [ meetings_channel ] on Zulip. You can find the up-to-date meeting times in
9
- [ the team calendar] ( ./calendar.md ) . Anyone can attend and it is recommended that compiler team
10
- members do.
9
+ During the weekly triage meeting the team considers backports, reviews performance triage reports
10
+ and discusses nominated issues. You can find the up-to-date meeting times in [ the team
11
+ calendar] ( ./calendar.md ) . Anyone can attend and it is recommended that compiler team members do.
11
12
12
13
Agendas of triage meetings are stored on [ HackMD] [ meeting_triage_notes ] .
13
14
@@ -16,8 +17,8 @@ See [*Prioritization*](./prioritization.md) for documentation on generating the
16
17
agenda.
17
18
18
19
## Steering/Planning Meeting
19
- The weekly steering/planning meeting also takes place on Zulip and is intended to host high-level
20
- discussions. Steering/planning meetings operate on a repeating schedule:
20
+ At a regular cadence, the team also meets to discuss high-level topics. Steering/planning meetings
21
+ operate on a repeating schedule:
21
22
22
23
- ** Week 1:** Planning meeting
23
24
- Select the topics for the next three meetings from the team's proposed meetings.
Original file line number Diff line number Diff line change @@ -195,9 +195,8 @@ After the meeting, there are a few closing tasks:
195
195
commit the agenda as minutes to the ` compiler-team ` repository.
196
196
- Remove the ` to-announce ` label from [ MCPs] [ mcps ] , unless this label was added exactly during
197
197
the meeting (and therefore will be seen during the following meeting).
198
- - Remove ` to-announce ` FCPs from [ ` rust-lang/rust ` repo] [ announce ] , [ ` compiler-team `
199
- repo] [ team_announce ] and [ forge repo] [ forge_announce ] . Same disclaimer as before regarding changes
200
- during the meeting.
198
+ - Remove ` to-announce ` FCPs from [ ` rust-lang/rust ` ] [ rust_announce ] , [ ` compiler-team ` ] [ team_announce ]
199
+ and the [ forge] [ forge_announce ] . Same disclaimer as before regarding changes during the meeting.
201
200
- Accept or decline [ ` beta nominated ` ] [ beta_nominated ] and [ ` stable nominated ` ] [ beta_nominated ]
202
201
backports that have been accepted during the meeting. For more info check [ ` t-release ` backporting
203
202
docs] [ release_backports ]
You can’t perform that action at this time.
0 commit comments