mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 08:25:20 +09:00
e8a688178c
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.)
1.4 KiB
1.4 KiB
title, category, layout, SPDX-License-Identifier
| title | category | layout | SPDX-License-Identifier |
|---|---|---|---|
| Steps to a Successful Release | Contributing | default | LGPL-2.1-or-later |
Steps to a Successful Release
- Add all items to NEWS
- Update the contributors list in NEWS (
ninja -C build git-contrib) - Update the time and place in NEWS
- Update hwdb (
ninja -C build update-hwdb update-hwdb-autosuspend) - [RC1] Update version and library numbers in
meson.build - Check dbus docs with
ninja -C build update-dbus-docs - Tag the release:
version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}" - Do
ninja -C build - Make sure that the version string and package string match:
build/systemctl --version - Upload the documentation:
ninja -C build doc-sync - [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
- "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
- Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
- Update IRC topic (
/msg chanserv TOPIC #systemd Version NNN released) - [FINAL] Push commits to stable, create an empty -stable branch:
git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).