mirror of
https://https.git.savannah.gnu.org/git/libtool.git
synced 2026-01-27 18:04:49 +00:00
9d99f7fdfd
* libtoolize.in: Overwrite function in bootstrap for printing version information for libtoolize. * build-aux/ltmain.in: Overwrite function in bootstrap for printing version information for libtool. * doc/libtool.texi: Fix typo and correct references for tests/demo subdirectory to the tests/demo.at Autotest file. * gl/top/README-release.diff: Add documentation for maintainers so the CVS repository is properly updated following a stable release.
52 lines
1.8 KiB
Diff
52 lines
1.8 KiB
Diff
--- gnulib/top/README-release
|
|
+++ README-release
|
|
@@ -1,5 +1,9 @@
|
|
Here are most of the steps we (maintainers) follow when making a release.
|
|
|
|
+* If you don't yet have gnu ftp upload rights, read this:
|
|
+
|
|
+ https://www.gnu.org/prep/maintain/html_node/Automated-Upload-Registration.html#Automated-Upload-Registration
|
|
+
|
|
* Start from a clean, up-to-date git directory on "master":
|
|
|
|
make -k maintainer-clean || { ./configure && make maintainer-clean; }
|
|
@@ -27,10 +31,25 @@ Here are most of the steps we (maintainers) follow when making a release.
|
|
|
|
./bootstrap && ./configure
|
|
|
|
+* Double check that serial number updates in public m4 files weren't
|
|
+ forgotten since last release (they should be updated in git along with
|
|
+ commits that require it so that users can work with git snapshots).
|
|
+
|
|
+* Update the LTDL_VERSION_INFO in libltdl/ltdl.mk for changes since
|
|
+ the last release.
|
|
+
|
|
+* Run "./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 distcheck DISTCHECK_CONFIGURE_FLAGS=--disable-ltdl-install
|
|
+ make distcheck DISTCHECK_CONFIGURE_FLAGS=--program-prefix=g
|
|
+ make distcheck DISTCHECK_CONFIGURE_FLAGS=--disable-shared
|
|
+ make distcheck CXX=g++
|
|
+
|
|
+ If there are any problems, fix them and start again.
|
|
|
|
* To (i) set the date, version number, and release TYPE on line 3 of
|
|
NEWS, (ii) commit that, and (iii) tag the release, run
|
|
@@ -98,4 +115,12 @@
|
|
|
|
to update the on-line manual accessible at
|
|
|
|
https://www.gnu.org/software/@PACKAGE@/manual/
|
|
+
|
|
+ Ensure that the on-line documentation links to the latest stable release:
|
|
+
|
|
+ https://www.gnu.org/software/@PACKAGE@/
|
|
+
|
|
+ On-line documentation is updated through the CVS repository:
|
|
+
|
|
+ https://savannah.gnu.org/cvs/?group=@PACKAGE@
|