gl/top/README-release.diff - master - githubmirror/libidn2

gl/top/README-release.diff
90 строк3 KB
Simon Josefsson
README-release.diff: Refresh gnulib patch
21 дек 2025, 02:36
21 дек 2025, 02:3643bf548
diff --git a/top/README-release b/top/README-release
index 5a8e8a59c1..9800cc7034 100644
--- a/top/README-release
+++ b/top/README-release
@@ -19,33 +19,36 @@ Here are most of the steps we (maintainers) follow when making a release.
 
     git push origin master
 
+* Check that the GitLab autobuilder is reporting all is well:
+
+    https://gitlab.com/libidn/libidn2/-/pipelines
+
 * Run the following command to download any new translations:
 
     ./bootstrap && ./configure
 
 * Pre-release testing: ensure that the following commands succeed:
 
-    c=check ve=check-very-expensive; git grep -q "^$ve:\$" && c=$ve
-    make $c syntax-check distcheck
+    make check syntax-check distcheck
 
 * To (i) set the date, version number, and release TYPE near the top of
   NEWS, (ii) commit that, and (iii) tag the release, run
 
     # "TYPE" must be stable, beta or alpha
-    make release-commit RELEASE='X.Y TYPE'
+    make release-commit RELEASE='X.Y.Z TYPE'
 
 * Run the following to create release tarballs.  Your choice selects the
   corresponding upload-to destination in the emitted gnupload command.
   The different destinations are specified in cfg.mk.  See the definitions
   of gnu_ftp_host-{alpha,beta,stable}.
 
-    make release RELEASE='X.Y TYPE'
+    make release RELEASE='X.Y.Z TYPE'
 
 * Test the tarball.  Copy it to a few odd-ball systems and ensure that
   it builds and passes all tests.
 
 * While that's happening, write the release announcement that you will
-  soon post.  Start with the template, $HOME/announce-@PACKAGE@-X.Y
+  soon post.  Start with the template, $HOME/announce-libidn2-X.Y.Z
   that was just created by that "make" command.
 
 Once all the builds and tests have passed,
@@ -53,7 +56,7 @@ Once all the builds and tests have passed,
 * Run the gnupload command that was suggested by your "make release"
   run above, or run
 
-    make upload RELEASE='X.Y TYPE'
+    make upload RELEASE='X.Y.Z TYPE'
 
 * Wait a few minutes (maybe up to 30?) and then use the release URLs to
   download all tarball/signature pairs and use gpg --verify to ensure
@@ -64,28 +67,6 @@ Once all the builds and tests have passed,
     v=$(cat .prev-version)
     git push origin master tag v$v
 
-* Announce it on Savannah first, so you can include the savannah.org
-  announcement link in the email message.
-
-  Go to the news-submission form:
-
-    https://savannah.gnu.org/news/submit.php?group=@PACKAGE@
-
-  If it does not work, then enable "News" for the project via this link:
-
-    https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=@PACKAGE@
-
-  Write something like the following:
-
-    Subject: @PACKAGE@-X.Y released [stable]
-    +verbatim+
-    ...paste the announcement here...
-    -verbatim-
-
-  Then go here to approve it:
-
-    https://savannah.gnu.org/news/approve.php?group=@PACKAGE@
-
 * Send the announcement email message.
 
 * After each non-alpha release, run
@@ -94,4 +75,4 @@ Once all the builds and tests have passed,
 
   to update the on-line manual accessible at
 
-    https://www.gnu.org/software/@PACKAGE@/manual/
+    https://www.gnu.org/software/libidn/libidn2/manual/