X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=doc%2Frelease.md;h=afe3033c288cffd8d95b06ea2e833989455cb81a;hb=df9f5e4b22383fda0eac689aa27bed7633e2b5f5;hp=eaa6a9af277d245788a5da2ab952929f15188ca4;hpb=cdb555f4fcdb57741ffb59bd2b0e66af69ea0a85;p=rust.git

diff --git a/doc/release.md b/doc/release.md
index eaa6a9af277..afe3033c288 100644
--- a/doc/release.md
+++ b/doc/release.md
@@ -94,13 +94,28 @@ After finding the Clippy commit, it can be tagged with the release number.
 # Assuming the current directory corresponds to the Clippy repository
 $ git checkout $SHA
 $ git tag rust-1.XX.0               # XX should be exchanged with the corresponding version
-$ git push upstream master --tags   # `upstream` is the `rust-lang/rust-clippy` remote
+$ git push upstream rust-1.XX.0     # `upstream` is the `rust-lang/rust-clippy` remote
 ```
 
 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`