Update CHANGES, Release and Announce prior to 2.3.4 release.

3 files changed, 14 insertions, 61 deletions

diff --git a/debian/changelog b/debian/changelog
index 5e4bf60..a39a73b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+scons (2.3.4) unstable; urgency=low
+
+  * Maintenance release.
+
+ -- Gary Oberbrunner <garyo@oberbrunner.com>  Sun, 27 Sep 2014 21:00:00 -0500
+
 scons (2.3.3) unstable; urgency=low
 
   * Maintenance release.
diff --git a/src/Announce.txt b/src/Announce.txt
index 6cb69b3..7c6fdd5 100644
--- a/src/Announce.txt
+++ b/src/Announce.txt
@@ -29,6 +29,7 @@ RELEASE VERSION/DATE TO BE FILLED IN LATER
   Please note the following important changes since release 2.3.3:
 
     -- Fix for EnsureSConsVersion regression in 2.3.3.
+
     -- Fix for interactive mode with Configure contexts
 
   Please note the following important changes since release 2.3.2:
diff --git a/src/RELEASE.txt b/src/RELEASE.txt
index 31c9590..853456d 100644
--- a/src/RELEASE.txt
+++ b/src/RELEASE.txt
@@ -1,73 +1,19 @@
-  A new SCons checkpoint release, 2.3.4.alpha.yyyymmdd, is now available
+  A new SCons checkpoint release, 2.3.4, is now available
   on the SCons download page:
 
           http://www.scons.org/download.php
 
-  XXX The primary purpose of this release ... XXX
+  This is a bug fix release to fix a regression in EnsureSConsVersion.
 
-  A SCons "checkpoint release" is intended to provide early access to
-  new features so they can be tested in the field before being released
-  for adoption by other software distributions.
-
-  Note that a checkpoint release is developed using the same test-driven
-  development methodology as all SCons releases.  Existing SCons
-  functionality should all work as it does in previous releases (except
-  for any changes identified in the release notes) and early adopters
-  should be able to use a checkpoint release safely for production work
-  with existing SConscript files.  If not, it represents not only a bug
-  in SCons but also a hole in the regression test suite, and we want to
-  hear about it.
-
-  New features may be more lightly tested than in past releases,
-  especially as concerns their interaction with all of the other
-  functionality in SCons.  We are especially interested in hearing bug
-  reports about new functionality.
-
-  We do not recommend that downstream distributions (Debian, Fedora,
-  etc.) package a checkpoint release, mainly to avoid confusing the
-  "public" release numbering with the long checkpoint release names.
-
-  Here is a summary of the changes since 1.3.0:
-
-  NEW FUNCTIONALITY
-
-    - List new features (presumably why a checkpoint is being released)
-
-  DEPRECATED FUNCTIONALITY
-
-    - List anything that's been deprecated since the last release
-
-  CHANGED/ENHANCED EXISTING FUNCTIONALITY
-
-    - List modifications to existing features, where the previous behavior
-      wouldn't actually be considered a bug
+  Here is a summary of the changes since 2.3.3
 
   FIXES
 
-    - List fixes of outright bugs
-
-  IMPROVEMENTS
-
-    - List improvements that wouldn't be visible to the user in the
-      documentation:  performance improvements (describe the circumstances
-      under which they would be observed), or major code cleanups
-
-  PACKAGING
-
-    - List changes in the way SCons is packaged and/or released
-
-  DOCUMENTATION
-
-    - List any significant changes to the documentation (not individual
-      typo fixes, even if they're mentioned in src/CHANGES.txt to give
-      the contributor credit)
-
-  DEVELOPMENT
-
-    - List visible changes in the way SCons is developed
+    - Fix regression in EnsureSConsVersion
 
-  Thanks to CURLY, LARRY, and MOE for their contributions to this release.
-  Contributors are listed alphabetically by their last name.
+  Thanks to Anatoly Techtonik and Russel Winder for their
+  contributions to this release.  Contributors are listed
+  alphabetically by their last name.
 
 __COPYRIGHT__
 __FILE__ __REVISION__ __DATE__ __DEVELOPER__