aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--.github/ISSUE_TEMPLATE/critical_nightly_regression.md17
-rw-r--r--docs/dev/README.md4
2 files changed, 21 insertions, 0 deletions
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 @@
1---
2name: Critical Nightly Regression
3about: You are using nightly rust-analyzer and the latest version is unusable.
4title: ''
5labels: ''
6assignees: 'matklad'
7
8---
9
10<!--
11Troubleshooting guide: https://rust-analyzer.github.io/manual.html#troubleshooting
12
13Please try to provide information which will help us to fix the issue faster. Minimal reproducible examples with few dependencies are especially lovely <3.
14-->
15
16This is a serious regression in nightly and it's important to fix it before the next release.
17@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
229Make sure to remove the new changelog post created when running `cargo xtask release` a second time. 229Make sure to remove the new changelog post created when running `cargo xtask release` a second time.
230 230
231We release "nightly" every night automatically and promote the latest nightly to "stable" manually, every week. 231We release "nightly" every night automatically and promote the latest nightly to "stable" manually, every week.
232
232We don't do "patch" releases, unless something truly egregious comes up. 233We don't do "patch" releases, unless something truly egregious comes up.
234To do a patch release, cherry-pick the fix on top of the current `release` branch and push the branch.
235There'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.
236Note: 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.
233 237
234## Permissions 238## Permissions
235 239