about summary refs log tree commit diff
diff options
context:
space:
mode:
authorflip1995 <philipp.krones@embecosm.com>2021-06-04 16:57:03 +0200
committerflip1995 <philipp.krones@embecosm.com>2021-06-04 16:57:03 +0200
commit52fc18c932eb9d0836fe2e158b9c689a1f623b79 (patch)
tree1789c3898856c6f665e07f0262435b03927742a9
parentb1752f616f532c068a19e8b690c31b5411be89cd (diff)
downloadrust-52fc18c932eb9d0836fe2e158b9c689a1f623b79.tar.gz
rust-52fc18c932eb9d0836fe2e158b9c689a1f623b79.zip
Release doc: add explanation for updating the stable branch
-rw-r--r--doc/release.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/release.md b/doc/release.md
index e0af9bf0625..afe3033c288 100644
--- a/doc/release.md
+++ b/doc/release.md
@@ -101,6 +101,21 @@ After this, the release should be available on the Clippy [release page].
 
 [release page]: https://github.com/rust-lang/rust-clippy/releases
 
+## Update the `stable` branch
+
+At this step you should have already checked out the commit of the `rust-1.XX.0`
+tag. Updating the stable branch from here is as easy as:
+
+```bash
+# Assuming the current directory corresponds to the Clippy repository and the
+# commit of the just created rust-1.XX.0 tag is checked out.
+$ git push upstream rust-1.XX.0:stable  # `upstream` is the `rust-lang/rust-clippy` remote
+```
+
+_NOTE: Usually there are no stable backports for Clippy, so this update should
+be possible without force pushing or anything like this. If there should have
+happened a stable backport, make sure to re-merge those changes just as with the
+`beta` branch._
 
 ## Update `CHANGELOG.md`