Here are a couple of distribution/release-related patches. Just pushed. There's plenty of room for additions and improvements in the new README-release file.
>From ce9c2c64de5798fbc17e6d64efc88fcdf9a039dc Mon Sep 17 00:00:00 2001 From: Jim Meyering <[email protected]> Date: Fri, 27 Feb 2009 13:56:49 +0100 Subject: [PATCH 1/2] dist: automate the post-release web-manual update process * maint.mk (web-manual): New rule, from m4's maint.mk. * bootstrap.conf (gnulib_modules): Add gendocs. --- bootstrap.conf | 1 + doc/.gitignore | 1 + maint.mk | 8 ++++++++ 3 files changed, 10 insertions(+), 0 deletions(-) diff --git a/bootstrap.conf b/bootstrap.conf index 9c385e4..446d611 100644 --- a/bootstrap.conf +++ b/bootstrap.conf @@ -57,6 +57,7 @@ gnulib_modules=" fsusage ftruncate ftello fts getdate getgroups gethrxtime + gendocs getline getloadavg getndelim2 getopt getpagesize getpass-gnu gettext gettime gettimeofday getugroups getusershell git-version-gen diff --git a/doc/.gitignore b/doc/.gitignore index 723a5a0..8d1fd24 100644 --- a/doc/.gitignore +++ b/doc/.gitignore @@ -16,6 +16,7 @@ coreutils.toc coreutils.tp coreutils.vr fdl.texi +gendocs_template getdate.texi stamp-vti version.texi diff --git a/maint.mk b/maint.mk index da5521e..ee279fe 100644 --- a/maint.mk +++ b/maint.mk @@ -862,3 +862,11 @@ alpha beta major: $(local-check) writable-files perl -pi -e '$$. == 3 and print "$(noteworthy)\n\n\n"' NEWS $(emit-commit-log) > .ci-msg $(VC) commit -F .ci-msg -a + +.PHONY: web-manual +web-manual: + @cd '$(srcdir)/doc'; \ + $(SHELL) ../build-aux/gendocs.sh -o '$(abs_builddir)/doc/manual' \ + --email $(PACKAGE_BUGREPORT) $(PACKAGE) \ + "$(PACKAGE_NAME) - Core GNU utilities" + @echo " *** Upload the doc/manual directory to web-cvs." -- 1.6.2.rc1.285.gc5f54 >From 59cec5af1277d335f1c63662ea6145f574c86beb Mon Sep 17 00:00:00 2001 From: Jim Meyering <[email protected]> Date: Sun, 1 Mar 2009 21:29:21 +0100 Subject: [PATCH 2/2] dist: document our release procedure * README-release: New file. --- README-release | 95 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 95 insertions(+), 0 deletions(-) create mode 100644 README-release diff --git a/README-release b/README-release new file mode 100644 index 0000000..59c084f --- /dev/null +++ b/README-release @@ -0,0 +1,95 @@ +Here are most of the steps we (maintainers) follow when making a release. + +* start from a clean, up-to-date git directory. + + git checkout master; git pull + +* Run ./configure && make maintainerclean + +* Ensure that the desired versions of autoconf, automake, bison, etc. + are in your PATH. + +* Ensure that you're on "master" with no uncommitted diffs. + This should produce no output: git checkout master; git diff + +* Make sure your local gnulib directory is up to date. + +* Run bootstrap, (assuming your local copy of gnulib is in /gnulib): + ./bootstrap --gnulib-srcdir=/gnulib + +FIXME: enable excluded programs like arch? to get their manual pages? + +* Pre-release testing: + On at least one SELinux-enabled (enforcing) and one non-SELinux system, + run all tests, both root-only and regular. + Run *all* non-root tests, including expensive and very expensive ones i.e., + run this: make check RUN_VERY_EXPENSIVE_TESTS=yes RUN_EXPENSIVE_TESTS=yes + + Run the root-only tests: + sudo env PATH="$PATH" NON_ROOT_USERNAME=$USER make -k check-root + +* Run "make distcheck" + +* Manually set the date, version number, and [stable/alpha/beta] on + line 3 of NEWS, then do this: + + v=7.1 + git commit -F <(printf 'version '$v'\n\n* NEWS: Record release date.\n') -a + git tag -s -m "coreutils $v" v$v HEAD + +* Run the following to create release tarballs. Your choice selects the + corresponding upload-to destination in the emitted gnupload command. + + # "TYPE" must be major, beta or alpha + XZ_OPT=-9e make 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. + +Once all the builds and tests have passed, + +* Run the gnupload command suggested by your "XZ_OPT=-9e make major" run above. + +* 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 new tag: + git push origin tag v<JUST_RELEASED_VERSION_NUMBER> + +* Send the gpg-signed announcement mail, e.g., + To: [email protected], [email protected] + Cc: [email protected], [email protected] + Subject: coreutils-7.1 released [stable] + +* Approve the announcement here: + http://lists.gnu.org/mailman/admindb/coreutils-announce + +* Announce it on Savannah, too: + From here: + https://savannah.gnu.org/projects/coreutils/ + click on the "submit news", then write something like the following: + + The announcement is here: + http://article.gmane.org/gmane.comp.gnu.core-utils.announce/48 + + Then go here to approve it: + https://savannah.gnu.org/news/approve.php?group=coreutils + +* For non-alpha releases, update the on-line manual at + + http://www.gnu.org/software/coreutils/manual/ + + Run `make web-manual', then copy the contents of doc/manual + into a CVS checkout of the coreutils manual repository. + Also edit coreutils.html (FIXME? why?) before doing a CVS commit. + + CVS_RSH=ssh \ + cvs -d:ext:[email protected]:/web/coreutils co coreutils + + Be sure to "cvs add" any files that "cvs status" marks with "?". + That is necessary whenever a new texinfo node is added. Each becomes + a new file in html_node that must then be "cvs add"ed. -- 1.6.2.rc1.285.gc5f54 _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
