ae_p scons.0
- aede {15}
+ aede {90}
- aerpass {15}
+ aerpass {90}
- aeib {15}
+ aeib {90}
aeb
START THE NEW BRANCH FOR RELEASE
- aenbr -p scons.0 {90}
+ aenbr -p scons.0 {91}
- aenc -p scons.0.{90}
+ aenc -p scons.0.{91}
Call it something like,
"Initialize the new branch for release."
Cause = internal_enhancement.
Exempt it from all tests (*_exempt = true).
- ae_p scons.0.{90}
+ ae_p scons.0.{91}
aedb 100
<your email>
cd incoming
bin
- put scons-0.90-1.noarch.rpm
- put scons-0.90-1.src.rpm
- put scons-0.90.tar.gz
- put scons-0.90.win32.exe
- put scons-0.90.zip
- put scons-local-0.90.tar.gz
- put scons-local-0.90.zip
- put scons-src-0.90.tar.gz
- put scons-src-0.90.zip
- put scons_0.90-1_all.deb
+ put scons-0.{91}-1.noarch.rpm
+ put scons-0.{91}-1.src.rpm
+ put scons-0.{91}.tar.gz
+ put scons-0.{91}.win32.exe
+ put scons-0.{91}.zip
+ put scons-local-0.{91}.tar.gz
+ put scons-local-0.{91}.zip
+ put scons-src-0.{91}.tar.gz
+ put scons-src-0.{91}.zip
+ put scons_0.{91}-1_all.deb
Create the new release at the SourceForge project page:
=> Add Release
- New release name: 0.90
+ New release name: 0.{91}
Cut-and-paste or upload the RELEASE.txt file.
Edit the file info:
- scons-0.90-1.noarch.rpm Any .rpm
- scons-0.90-1.src.rpm Any Source .rpm
- scons-0.90.tar.gz Any .gz
- scons-0.90.win32.exe i386 .exe (32-bit Windows)
- scons-0.90.zip Any .zip
- scons_0.90-1_all.deb Any .deb
+ scons-0.{91}-1.noarch.rpm Any .rpm
+ scons-0.{91}-1.src.rpm Any Source .rpm
+ scons-0.{91}.tar.gz Any .gz
+ scons-0.{91}.win32.exe i386 .exe (32-bit Windows)
+ scons-0.{91}.zip Any .zip
+ scons_0.{91}-1_all.deb Any .deb
Click "Update/Refresh" for each file; this must be done
one at a time.
=> Add Release
- New release name: 0.90
+ New release name: 0.{91}
Cut-and-paste or upload the RELEASE.txt file.
Edit the file info:
- scons-local-0.90.tar.gz Any .gz
- scons-local-0.90.zip Any .zip
+ scons-local-0.{91}.tar.gz Any .gz
+ scons-local-0.{91}.zip Any .zip
Click "Update/Refresh" for each file; this must be done
one at a time.
=> Add Release
- New release name: 0.90
+ New release name: 0.{91}
Cut-and-paste or upload the RELEASE.txt file.
Edit the file info:
- scons-src-0.90.tar.gz Any .gz
- scons-src-0.90.zip Any .zip
+ scons-src-0.{91}.tar.gz Any .gz
+ scons-src-0.{91}.zip Any .zip
Click "Update/Refresh" for each file; this must be done
one at a time.
Release Notice section.
- Hide release {0.13} at the SourceForge download page:
+ Hide release {0.14} at the SourceForge download page:
Go to the Admin page
=> Edit Releases
- Release Name: {0.13}
+ Release Name: {0.14}
=> Edit This Release
=> Edit Releases
- Release Name: {0.13}
+ Release Name: {0.14}
=> Edit This Release
=> Edit Releases
- Release Name: {0.13}
+ Release Name: {0.14}
=> Edit This Release
- In the Bugs Tracker, add a Group for the new release (0.90)
+ In the Bugs Tracker, add a Group for the new release (0.91)
=======================
Template describe-the-release section:
-IMPORTANT: Release 0.90 contains the following interface changes:
+IMPORTANT: Release 0.91 contains the following interface changes:
- XXX
See the release notes for more information about these changes.
SConspirators--
-SCons alpha release 0.90 is now available for download.
+SCons alpha release 0.91 is now available for download.
XXX Template describe-the-release section goes here XXX
=======================
Template scons-users + scons-announce announcement:
-Version 0.90 of SCons has been released and is available for download
+Version 0.91 of SCons has been released and is available for download
from the SCons web site:
http://www.scons.org/
in Python. It is based on the design which won the Software Carpentry
build tool competition in August 2000.
-Version 0.90 of SCons has been released and is available for download
+Version 0.91 of SCons has been released and is available for download
from the SCons web site:
http://www.scons.org/
-RELEASE 0.90 - Wed, 25 Jun 2003 14:24:52 -0500
+RELEASE 0.XX - XXX
- This is the first beta release of SCons. Please consult the
+ This is the second beta release of SCons. Please consult the
CHANGES.txt file for a list of specific changes since last release.
+ Please note the following important changes since release 0.90:
+
Please note the following important changes since release 0.14:
- SCons now tries to verify that Microsoft Visual Studio (including
a default directory that we have not seen before. If this is the
case, please let us know so that we can update future versions.
- Please note the following important changes since release 0.13:
-
- - Tool specifications no longer take a "platform" argument. You
- will need to remove this argument if you define any local Tool
- specifications. The new env['PLATFORM'] construction variable can
- now be used to find the string that used to be passed in as the
- "platform" argument.
-
- - Emitter functions in Builders are now passed Node objects, not
- strings, for all targets and sources. Your emitter may need to
- use the str() function to examine the names of specified files.
-
- - The SetBuildSignatureType() and SetContentSignatureType() functions
- have been deprecated. The new names are TargetSignatures() and
- SourceSignatures().
-
- - The Export() function and the exported variables argument of
- SConscript() now search for variables using the same rules as
- Python: local first, then global. If you are calling Export() or
- SConscript() from a module imported directly into an SConscript
- file, you may need to modify the module to make the previously
- global variables available to your Export() or SConscript() call.
-
- - The SetJobs() and GetJobs() functions have been deprecated.
- Their new equivalents are:
-
- SetOption('num_jobs', num)
- GetOption('num_jobs')
-
- - Callable expansions of construction variables in a command line
- now take a fourth "for_signature" argument that is set when the
- expansion is being called to generate a build signature.
-
- - Construction variables for building a target are now frozen when the
- Builder is called; later changes to the Environment do not
- necessarily affect how the target is build. You may need to
- re-order statements in your SConscript files to make sure
- construction variables are set before calling the Builders that will
- use them.
-
SCons is developed with an extensive regression test suite, and a
rigorous development methodology for continually improving that suite.
Because of this, SCons is of sufficient quality that you can use it
projects / scons.git / commitdiff