summaryrefslogtreecommitdiff
path: root/docs/RELEASE.md
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-04-03 16:43:17 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-04-03 16:43:17 +0200
commit3be493914962ad515df90de70781f93cd809af89 (patch)
treedc9023f7fb42c1ea1b28450cee45bae4e9c827c3 /docs/RELEASE.md
parentafa4e4a9db0482e965b5e28c9deeaa0c2a3708e2 (diff)
downloadsystemd-3be493914962ad515df90de70781f93cd809af89.tar.gz
docs: also document updates to stable repo
Diffstat (limited to 'docs/RELEASE.md')
-rw-r--r--docs/RELEASE.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 0b1b230296..d842afcd34 100644
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -16,3 +16,4 @@ title: Steps to a Successful Release
10. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
11. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
12. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
+13. [After final release] Also push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:v${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).