From 27073f4fc3e967339eb08b9c2b0899639dd6e618 Mon Sep 17 00:00:00 2001 From: Aleksey Kladov Date: Thu, 22 Apr 2021 11:15:20 +0300 Subject: feat: make sure nightly regressions don't break users --- .github/ISSUE_TEMPLATE/critical_nightly_regression.md | 17 +++++++++++++++++ docs/dev/README.md | 4 ++++ 2 files changed, 21 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/critical_nightly_regression.md diff --git a/.github/ISSUE_TEMPLATE/critical_nightly_regression.md b/.github/ISSUE_TEMPLATE/critical_nightly_regression.md new file mode 100644 index 000000000..a0b1627d7 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/critical_nightly_regression.md @@ -0,0 +1,17 @@ +--- +name: Critical Nightly Regression +about: You are using nightly rust-analyzer and the latest version is unusable. +title: '' +labels: '' +assignees: 'matklad' + +--- + + + +This is a serious regression in nightly and it's important to fix it before the next release. +@matklad, please take a look. diff --git a/docs/dev/README.md b/docs/dev/README.md index 7e4488a41..b98ac4c0a 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -229,7 +229,11 @@ If it fails because of something that needs to be fixed, remove the release tag Make sure to remove the new changelog post created when running `cargo xtask release` a second time. We release "nightly" every night automatically and promote the latest nightly to "stable" manually, every week. + We don't do "patch" releases, unless something truly egregious comes up. +To do a patch release, cherry-pick the fix on top of the current `release` branch and push the branch. +There's no need to write a changelog for a patch release, it's OK to include the notes about the fix into the next weekly one. +Note: we tag releases by dates, releasing a patch release on the same day should work (by overwriting a tag), but I am not 100% sure. ## Permissions -- cgit v1.2.3