Simplify the release process

Aperta
  • Qualcosa non va?
#5,187 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, rust
Ambito
ci-cd, release

Direzione di ricerca

Start by reading the existing release instructions and GitHub CI workflows that handle beta and stable releases; the issue does not name specific files. Map the manual steps for rustup-init.sh, the stable branch, and publication through t-release, then identify which steps can be safely triggered together. Done means one release trigger automates the agreed steps without making CI workflows too hard to debug.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

It is clear that with the 1.29.2 release our release process has become a bottleneck in terms of DX.

In other projects I maintain, making a release is as simple as adding a tag: GitHub CI will handle the rest. However, this is more complicated for rustup because:

  • We have 2 stages (beta/stable) rule to push to two different environments.
  • There are more markdown files to write.
  • t-release is involved for the final publication.

Main burdens

  • Having to handle 2 stages: this means a lot of work will have to be done twice for every version number
  • Requiring a separate PR to bump rustup-init.sh and its E2E test snapshot for every given release, which is currently painfully manual
  • Having to write 3 different but similar markdown posts: changelog, forum post (beta stage) and announcement post (stable stage) and syncing between them
  • Manually maintaining the stable branch
  • Patiently waiting for the stable CI/CD to turn green
  • Remembering to tag the stable release when everything is done with the stable stage

Expected outcome

One trigger that does almost everything, ideally without t-rustup human interaction afterwards.

Ideas

Some random ideas for automation include:

  • Using tags as CI triggers, or provide explicit CI triggers to start the release automation (with the automatic creation of the tag at the end)
  • Using the name of the tag to distinguish beta/release stages
  • The automation then automatically bumps rustup-init.sh and maintains stable
  • The automation could, at the same time, accept markdown input (from the changelog maybe?) so that we can copy-paste as the corresponding forum/announcement post
    • The post part may better not be automated because we may not want to add the forum post for emergency releases, or we may want to slightly adjust the wording for certain posts.
  • When the stable CI turns green, we may want to hook some Zulip bot here to indicate that we can move on to the next step

But the crucial point is that we don't want to go too far on this since GitHub CI workflows are famously hard to debug.

Lingua principale
Rust
Stelle
7.1k
Fork
1.1k
Merge medio
1g 3h
PR unite (30g)
38

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rust-lang/rustup

Tutte le issue di rust-lang/rustup

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.