mirror of
https://git.savannah.gnu.org/git/gnulib.git
synced 2025-08-17 12:41:05 +03:00
b9a38b4535
See <http://lists.gnu.org/archive/html/bug-gnulib/2012-08/msg00028.html>. Do not depend simply on the current $(VERSION), as there may have been new commits since the tarball generation. Rather, rely on $(RELEASE), as "make release-commit" already does. For consistency, add "make release RELEASE='X.Y TYPE'" as an alias for "make TYPE". * top/maint.mk (upload_command, upload, release): New. (RELEASE_TYPE): If undefined, default to the second word of $(RELEASE). (VERSION): first word of $(RELEASE) is always right. (emit_upload_commands): Adjust. * top/README-release: Update.
101 lines
2.9 KiB
Plaintext
101 lines
2.9 KiB
Plaintext
Here are most of the steps we (maintainers) follow when making a release.
|
|
|
|
* Start from a clean, up-to-date git directory on "master":
|
|
|
|
make -k maintainer-clean || { ./configure && make maintainer-clean; }
|
|
git checkout master
|
|
git pull origin master
|
|
|
|
* Ensure that the latest stable versions of autoconf, automake, etc.
|
|
are in your PATH. See the buildreq list in bootstrap.conf for
|
|
the complete list of tools.
|
|
|
|
* Ensure that you have no uncommitted diffs. This should produce no
|
|
output:
|
|
|
|
git diff
|
|
|
|
* Ensure that you've pushed all changes that belong in the release:
|
|
|
|
git push origin master
|
|
|
|
* Check that the NixOS/Hydra autobuilder is reporting all is well:
|
|
|
|
http://hydra.nixos.org/jobset/gnu/@PACKAGE@-master
|
|
|
|
* Run the following command to download any new translations:
|
|
|
|
./bootstrap && ./configure
|
|
|
|
* Pre-release testing: ensure that the following command succeeds:
|
|
|
|
make check syntax-check distcheck
|
|
|
|
* To (i) set the date, version number, and release TYPE on line 3 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'
|
|
|
|
* 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'
|
|
|
|
* 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
|
|
that was just created by that "make" command.
|
|
|
|
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'
|
|
|
|
* 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
|
|
that they're all valid.
|
|
|
|
* Push the NEWS-updating changes and the new tag:
|
|
|
|
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
|
|
|
|
make web-manual-update
|
|
|
|
to update the on-line manual accessible at
|
|
|
|
http://www.gnu.org/software/@PACKAGE@/manual/
|