diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-04-12 12:05:53 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-04-12 12:35:44 +0200 |
| commit | e8a688178c4875f3b67e5fbc6e56d0487258f535 (patch) | |
| tree | 5d7959e2578e30ae372db15a883ec1d0c1d9351f /docs/RELEASE.md | |
| parent | man: add page for sd_device_{ref,unref,unrefp} (diff) | |
| download | systemd-e8a688178c4875f3b67e5fbc6e56d0487258f535.tar.xz systemd-e8a688178c4875f3b67e5fbc6e56d0487258f535.zip | |
docs: stop recommending meson compile
With meson-0.60, meson compile stopped working with some targets:
$ meson compile -C build update-man-rules
ERROR: Can't invoke target `update-man-rules`: ambiguous name. Add target type and/or path: `PATH/NAME:TYPE`
This is obviously a regression in meson, but based on a chat with the
maintainers, it seems that there's some disagreement as to whether 'meson
compile' is useful and how exactly it should work. Since we're already at
meson 0.60.3 and this hasn't been fixed, and people generally don't seem to
consider this an issue, let's return to documenting the usual practice of
'ninja -C build' that just works everywhere.
(Since nobody has raised any fuss in systemd, it means that people are
generally using the shorter form during development too. I only noticed
because I pasted a command from the release docs when preparing -rc1.)
Diffstat (limited to 'docs/RELEASE.md')
| -rw-r--r-- | docs/RELEASE.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/RELEASE.md b/docs/RELEASE.md index c5da09b62c..a5ab146f28 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -8,15 +8,15 @@ SPDX-License-Identifier: LGPL-2.1-or-later # Steps to a Successful Release 1. Add all items to NEWS -2. Update the contributors list in NEWS (`meson compile -C build git-contrib`) +2. Update the contributors list in NEWS (`ninja -C build git-contrib`) 3. Update the time and place in NEWS -4. Update hwdb (`meson compile -C build update-hwdb update-hwdb-autosuspend`) +4. Update hwdb (`ninja -C build update-hwdb update-hwdb-autosuspend`) 5. [RC1] Update version and library numbers in `meson.build` -6. Check dbus docs with `meson compile -C build update-dbus-docs` +6. Check dbus docs with `ninja -C build update-dbus-docs` 7. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"` -8. Do `meson compile -C build` +8. Do `ninja -C build` 9. Make sure that the version string and package string match: `build/systemctl --version` -10. Upload the documentation: `meson compile -C build doc-sync` +10. Upload the documentation: `ninja -C build doc-sync` 11. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones) 12. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate. 13. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically. |