faccessat: speed up 'configure' on mainstream hosts

[gnulib.git] / top / README-release

diff --git a/top/README-release b/top/README-release
index 680547b..17f026a 100644 (file)
--- a/top/README-release
+++ b/top/README-release
@@ -1,6 +1,6 @@
 Here are most of the steps we (maintainers) follow when making a release.
 
 Here are most of the steps we (maintainers) follow when making a release.
 

-* Start from a clean, up-to-date git directory:
+* Start from a clean, up-to-date git directory on "master":

 
     make -k maintainer-clean || { ./configure && make maintainer-clean; }
     git checkout master
 
     make -k maintainer-clean || { ./configure && make maintainer-clean; }
     git checkout master


@@ -10,10 +10,10 @@ Here are most of the steps we (maintainers) follow when making a release.
   are in your PATH.  See the buildreq list in bootstrap.conf for
   the complete list of tools.
 
   are in your PATH.  See the buildreq list in bootstrap.conf for
   the complete list of tools.
 

-* Ensure that you're on "master" with no uncommitted diffs.
-  This should produce no output:
+* Ensure that you have no uncommitted diffs.  This should produce no
+  output:

 
 

-    git checkout master; git diff
+    git diff

 
 * Ensure that you've pushed all changes that belong in the release:
 
 
 * Ensure that you've pushed all changes that belong in the release:
 


@@ -31,18 +31,18 @@ Here are most of the steps we (maintainers) follow when making a release.
 
     make check syntax-check distcheck
 
 
     make check syntax-check distcheck
 

-* Set the date, version number, and release type [stable/alpha/beta] on
-  line 3 of NEWS, commit that, and tag the release by running e.g.,
+* To (i) set the date, version number, and release TYPE on line 3 of
+  NEWS, (ii) commit that, and (iii) tag the release, run

 
 

-    build-aux/do-release-commit-and-tag X.Y stable
+    # "TYPE" must be stable, beta or alpha
+    make release-commit RELEASE='X.Y 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}.
 
 
 * 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}.
 

-    # "TYPE" must be stable, beta or alpha
-    make TYPE
+    make release RELEASE='X.Y TYPE'

 
 * Test the tarball.  Copy it to a few odd-ball systems and ensure that
   it builds and passes all tests.
 
 * Test the tarball.  Copy it to a few odd-ball systems and ensure that
   it builds and passes all tests.


@@ -53,7 +53,10 @@ Here are most of the steps we (maintainers) follow when making a release.
 
 Once all the builds and tests have passed,
 
 
 Once all the builds and tests have passed,
 

-* Run the gnupload command that was suggested by your "make TYPE" run above.
+* Run the gnupload command that was suggested by your "make release"
+  run above, or run
+
+    make upload RELEASE='X.Y 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
 
 * 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


@@ -67,12 +70,15 @@ Once all the builds and tests have passed,
 * Announce it on Savannah first, so you can include the savannah.org
   announcement link in the email message.
 
 * Announce it on Savannah first, so you can include the savannah.org
   announcement link in the email message.
 

-  From here:
-    https://savannah.gnu.org/projects/@PACKAGE@/
-  click on "submit news", then write something like the following:
-  (If there is no such button, then enable "News" for the project via
-   the Main -> "Select Features" menu item, or via this link:
-   https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=@PACKAGE@)
+  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+
 
     Subject: @PACKAGE@-X.Y released [stable]
     +verbatim+


@@ -80,14 +86,15 @@ Once all the builds and tests have passed,
     -verbatim-
 
   Then go here to approve it:
     -verbatim-
 
   Then go here to approve it:

+

     https://savannah.gnu.org/news/approve.php?group=@PACKAGE@
 
 * Send the announcement email message.
 
     https://savannah.gnu.org/news/approve.php?group=@PACKAGE@
 
 * Send the announcement email message.
 

-* After each non-alpha release, update the on-line manual accessible via
+* After each non-alpha release, run

 
 

-    http://www.gnu.org/software/@PACKAGE@/manual/
+    make web-manual-update

 
 

-  by running this:
+  to update the on-line manual accessible at

 
 

-    build-aux/gnu-web-doc-update
+    http://www.gnu.org/software/@PACKAGE@/manual/