mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 18:23:32 +08:00
docs: Use v255~rc1 instead of v255-rc1
This gets the point across better that we want the rc to sort lower than the official release.
This commit is contained in:
parent
37c6c2035e
commit
c0561a05f5
@ -15,7 +15,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
|
||||
6. [RC1] Update version and library numbers in `meson.build`
|
||||
7. Check dbus docs with `ninja -C build update-dbus-docs`
|
||||
8. Update translation strings (`cd build`, `meson compile systemd-pot`, `meson compile systemd-update-po`) - drop the header comments from `systemd.pot` + re-add SPDX before committing. If the only change in a file is the 'POT-Creation-Date' field, then ignore that file.
|
||||
9. Tag the release: `version=vXXX~rcY && git tag -s "${version}" -m "systemd ${version}"`. Note that this uses a tilde (\~) instead of a hyphen (-) because tildes sort lower in version comparisons according to the [version format specification](https://uapi-group.org/specifications/specs/version_format_specification/), and we want `v255-rc1` to sort lower than `v255`.
|
||||
9. Tag the release: `version=vXXX~rcY && git tag -s "${version}" -m "systemd ${version}"`. Note that this uses a tilde (\~) instead of a hyphen (-) because tildes sort lower in version comparisons according to the [version format specification](https://uapi-group.org/specifications/specs/version_format_specification/), and we want `v255~rc1` to sort lower than `v255`.
|
||||
10. Do `ninja -C build`
|
||||
11. Make sure that the version string and package string match: `build/systemctl --version`
|
||||
12. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
|
||||
|
Loading…
Reference in New Issue
Block a user