diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-04-03 16:23:43 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-04-03 16:23:43 +0200 |
| commit | afa4e4a9db0482e965b5e28c9deeaa0c2a3708e2 (patch) | |
| tree | 71575eaafff60610fad2257c955e236e5ac6b04d /docs | |
| parent | 3b4ce4b08c5143b2d5ff00970444ee4183298e63 (diff) | |
| download | systemd-afa4e4a9db0482e965b5e28c9deeaa0c2a3708e2.tar.gz | |
docs: let's not close the milestone early
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/RELEASE.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/RELEASE.md b/docs/RELEASE.md index 583d5d4d4a..0b1b230296 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -12,7 +12,7 @@ title: Steps to a Successful Release 6. Do `ninja -C build` 7. Make sure that the version string and package string match: `build/systemctl --version` 8. Upload the documentation: `ninja -C build doc-sync` -9. Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones) +9. [After final release] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones) 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`) |