From 774b6995220a3f0010b16df92ef38d3556fd49f3 Mon Sep 17 00:00:00 2001
From: Olivier Fourdan <ofourdan@redhat.com>
Date: Tue, 13 Sep 2022 09:18:55 +0200
Subject: [PATCH] releasing: Use the release script from wayland
The release script from the Wayland repository is simpler than the
script from Xorg, uses the releases from gitlab and is now generic
enough to be used by different projects.
Update the release procedure to use that script instead.
Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
Reviewed-by: Simon Ser <contact@emersion.fr>
---
releasing.md | 17 +++++------------
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/releasing.md b/releasing.md
index a92e240..70b80e8 100644
--- a/releasing.md
+++ b/releasing.md
@@ -15,26 +15,19 @@ To make a release of wayland-utils, follow these steps.
2. Run the `release.sh` script to generate the tarballs, sign and upload them,
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
- release. If the script fails on the distcheck step due to a test suite error
- that can't be fixed for some reason, you can skip testsuite by specifying
- the `--dist` argument. Pass `--help` to see other supported options.
-
- $ release.sh .
-
-3. 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
+3. Compose the release announcements. The script will generate a *-x.y.z-announce.eml
+ file with a list of changes and tags. Prepend these with a human-readable
listing of the most notable changes.
4. PGP sign the release announcement and send it to
<wayland-devel@lists.freedesktop.org>.
5. 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:
--
GitLab