8621: feat: make sure nightly regressions don't break users r=lnicola a=matklad



Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
This commit is contained in:
bors[bot] 2021-04-22 08:29:01 +00:00 committed by GitHub
commit d1c9bd134d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 0 deletions

View file

@ -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'
---
<!--
Troubleshooting guide: https://rust-analyzer.github.io/manual.html#troubleshooting
Please try to provide information which will help us to fix the issue faster. Minimal reproducible examples with few dependencies are especially lovely <3.
-->
This is a serious regression in nightly and it's important to fix it before the next release.
@matklad, please take a look.

View file

@ -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. 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 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. 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 ## Permissions