[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH 2/3] Release Version 2.68b.

From: Eric Blake
Subject: [PATCH 2/3] Release Version 2.68b.
Date: Thu, 1 Mar 2012 21:47:04 -0700

It's been more than a year since 2.68; time for a beta release
to shake out any last minute bugs, before a release of 2.69
in the near future.

* NEWS: Mention the release.
* HACKING: Update some instructions.

Signed-off-by: Eric Blake <address@hidden>
 HACKING |   20 +++++++++-----------
 NEWS    |    3 ++-
 2 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/HACKING b/HACKING
index 7a98fcb..58a50a9 100644
@@ -50,14 +50,13 @@ release:

 - Run `make syntax-check'
   This makes sure that the source files follow some consistent rules.
-  The checks live in, which is intended to be shared across
-  several projects.  (Help in merging this to use gnulib's
-  would be appreciated).
+  The checks live in, shared from gnulib, and customized in

-- Run `make maintainer-distcheck'
-  This is quite long.  It basically runs the test suite using a C++
-  compiler instead of a C compiler, and within a severe environment
+- Run `make distcheck'
+- Test some unusual environments, such as building and running the
+  testsuite with POSIXLY_CORRECT=1 CC=g++.

 - Try some real world packages
   A good example is the coreutils package.
@@ -108,9 +107,7 @@ Update the version number in NEWS (with version, date, and 
 type) and ChangeLog, and mention in README whether the release is
 stable.  Make sure all changes are committed, then run `git tag -s -m
 <version> -u <gpg_key> v<version>'.  Do not push anything upstream at
-this point.  At this point, running `make _version', followed by `make
-news-date-check changelog-check' will validate that the information is
-formatted correctly.
+this point.

 ** Update configure
 As much as possible, make sure to release an Autoconf that uses
@@ -139,7 +136,8 @@ Run `git push origin refs/tags/v<version>' to push the 
release tag.
 ** Announce
 Complete/fix the announcement file, and email it at least to
 address@hidden and address@hidden  If this is a stable
-release, also mail to address@hidden
+release, also mail to address@hidden; if it is a beta release,
+also mail to address@hidden

 ** Other web updates
 For alpha and beta releases, the process is complete.  For stable
diff --git a/NEWS b/NEWS
index 1a5f775..773a7b8 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,7 @@
 GNU Autoconf NEWS - User visible changes.

-* Noteworthy changes in release ?.? (????-??-??) [?]
+* Noteworthy changes in release 2.68b (2012-03-01) [beta]
+  Released by Eric Blake, based on git versions 2.68.*.

 ** Autoconf-generated configure scripts now unconditionally re-execute
    themselves with $CONFIG_SHELL, if that's set in the environment.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]