aboutsummaryrefslogtreecommitdiff
path: root/docs/dev
diff options
context:
space:
mode:
authorAleksey Kladov <[email protected]>2021-04-22 09:15:20 +0100
committerAleksey Kladov <[email protected]>2021-04-22 09:15:20 +0100
commit27073f4fc3e967339eb08b9c2b0899639dd6e618 (patch)
tree8f77c354e3f9a6e02062cbd75ac5ba5684839469 /docs/dev
parent7ae0bc1bd40286200f5e5b7a4d3b086312055ed5 (diff)
feat: make sure nightly regressions don't break users
Diffstat (limited to 'docs/dev')
-rw-r--r--docs/dev/README.md4
1 files changed, 4 insertions, 0 deletions
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