shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-24 21:34:08 +03:00
Code
e1aec57dd1
systemd-stable/docs/RELEASE.md
Zbigniew Jędrzejewski-Szmek 4c890ad3cc meson: rename target to update-dbus-docs 
Very old versions of meson did not include the subdirectory name in the
target name, so we started adding various "top-level" custom targets in
subdirectories. This was nice because the main meson.build file wasn't
as cluttered. But then meson started including the subdir name in the
target name. So let's move the definition to the root so we can have all
targets named uniformly.
2021-01-27 08:46:42 +01:00

1.3 KiB
Raw Blame History

title category layout
Steps to a Successful Release Contributing default

Steps to a Successful Release

  1. Add all items to NEWS
  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 meson compile -C build update-dbus-docs
  6. Tag the release: version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"
  7. Do meson compile -C build
  8. Make sure that the version string and package string match: build/systemctl --version
  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.
  13. Update IRC topic (/msg chanserv TOPIC #systemd Version NNN released)
  14. [FINAL] Push commits to stable, create an empty -stable branch: git push systemd-stable origin/master:master origin/master:refs/heads/${version}-stable, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).