releasing: use the Wayland release script

See [1] for the motivation.

[1]: 7cdc20cee6

Signed-off-by: Simon Ser <contact@emersion.fr>
This commit is contained in:
Simon Ser 2022-09-06 12:26:43 +02:00 committed by Marius Vlad
parent fb57ce17ef
commit f6cbb6678c
1 changed files with 10 additions and 17 deletions

View File

@ -26,27 +26,20 @@ To make a release of Weston, follow these steps.
3. Run the `release.sh` script to generate the tarballs, sign and upload them, 3. Run the `release.sh` script to generate the tarballs, sign and upload them,
and generate a release announcement template. This script can be obtained and generate a release announcement template. This script can be obtained
from X.org's modular package: from the Wayland repository:
https://gitlab.freedesktop.org/xorg/util/modular/blob/master/release.sh https://gitlab.freedesktop.org/wayland/wayland/-/blob/main/release.sh
The script supports a `--dry-run` option to test it without actually doing a 4. Compose the release announcements. The script will generate a
release. If the script fails on the distcheck step due to a test suite error weston-x.y.z.announce file with a list of changes and tags. Prepend these
that can't be fixed for some reason, you can skip testsuite by specifying with a human-readable listing of the most notable changes. For x.y.0
the `--dist` argument. Pass `--help` to see other supported options. releases, indicate the schedule for the x.y+1.0 release.
release.sh . 5. PGP sign the release announcement and send it to
5. Compose the release announcements. The script will generate *.x.y.z.announce
files with a list of changes and tags. Prepend these with a human-readable
listing of the most notable changes. For x.y.0 releases, indicate the
schedule for the x.y+1.0 release.
6. PGP sign the release announcement and send it to
<wayland-devel@lists.freedesktop.org>. <wayland-devel@lists.freedesktop.org>.
7. Update `releases.html` in wayland.freedesktop.org with links to tarballs and 6. Update `releases.html` in wayland.freedesktop.org with links to tarballs and
the release email URL. Copy tarballs produced by `release.sh` to `releases/`. the release email URL.
Once satisfied: Once satisfied: