diff options
| author | Lennart Poettering <lennart@poettering.net> | 2020-12-11 11:33:39 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2020-12-17 16:51:48 +0100 |
| commit | 8b08be4052fa51a9ad0de8a6f9213efe4dac213d (patch) | |
| tree | 710fb0a1db155393094eccd9fda1eca13eea9b0f /docs/RELEASE.md | |
| parent | 68f18549c551d677d97ebd18d27827e1613a06a7 (diff) | |
| download | systemd-8b08be4052fa51a9ad0de8a6f9213efe4dac213d.tar.gz | |
tree-wide: suggest meson command lines instead of ninja ones
This only changes documentation. In various places we call "ninja"
directly. I figured it would be safer to leave those in place for now,
given the meson replacement commands lines appears to be supported in
newer meson versions only.
Diffstat (limited to 'docs/RELEASE.md')
| -rw-r--r-- | docs/RELEASE.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/RELEASE.md b/docs/RELEASE.md index a93c0c6418..5914464107 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -7,14 +7,14 @@ layout: default # Steps to a Successful Release 1. Add all items to NEWS -2. Update the contributors list in NEWS (`ninja -C build git-contrib`) +2. Update the contributors list in NEWS (`meson compile -C build git-contrib`) 3. Update the time and place in NEWS 4. [RC1] Update version and library numbers in `meson.build` -5. Check dbus docs with `ninja -C build man/update-dbus-docs` +5. Check dbus docs with `meson compile -C build man/update-dbus-docs` 6. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"` -7. Do `ninja -C build` +7. Do `meson compile -C build` 8. Make sure that the version string and package string match: `build/systemctl --version` -9. Upload the documentation: `ninja -C build doc-sync` +9. Upload the documentation: `meson compile -C build doc-sync` 10. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones) 11. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate. 12. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically. |