we should add a builder that runs the test suite on linux with--release-channel=stable, to catch early tests that depend on nightly being the channel(like the rustdoc ones)
Assigned: Mark
we really need to stop reverting things on beta while keeping them on nightly, if something is broken on beta we should revert it on nightly and then reland it along with the fix
Tracking what has landed onto what branch is pretty painful with GitHub, no great tooling exists
Maybe we need to invest here in some alternative platform or solution
need to track by version number, not branch, since we can be in the midst of promotion
issue open/closed by version number, with associated PR
Assigned: Mark to file issue to start getting a list of requirements put together, and we can maybe go to internals and ask if there’s something out there meeting those needs
we should have milestones added to all regression- issue
we may want to switch to a single label, regression, plus a milestone
put channel names in the milestone itself?
should be something to integrate into triagebot
Assigned: Mark to file an issue and potentially implement channel-named milestones in triagebot
this would let us migrate to just a regression label over time, without needing as much synchronization
Kickoff a doc we can record any release todos into quickly(or a locked issue, just something). Reverting across 3 branches can take some work and time and needs tracking, for example.
Assigned:
Install tidy on the release machines so you get a diff when rustdoc tests fail. That would have narrowed down that the failure was from a channel-specific change.
Every meeting
2021-07-09
2021-05-21
2021-05-07