Simplify the release process

オープン
  • 何か問題がありますか？
#5,187 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, rust
領域
ci-cd, release

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
7.1k
フォーク
1.1k
平均マージ
1日 3時間
マージ済み PR（30日）
38

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

rust-lang/rustup のほかの issue

rust-lang/rustup の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。