diff options
Diffstat (limited to 'src/RELEASE.txt')
-rw-r--r-- | src/RELEASE.txt | 27 |
1 files changed, 2 insertions, 25 deletions
diff --git a/src/RELEASE.txt b/src/RELEASE.txt index 07eaaf4..f87f889 100644 --- a/src/RELEASE.txt +++ b/src/RELEASE.txt @@ -3,35 +3,12 @@ http://www.scons.org/download.php - XXX The primary purpose of this release ... XXX - 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: + Here is a summary of the changes since 2.5.1: NEW FUNCTIONALITY - - List new features (presumably why a checkpoint is being released) + - Initial support for Python 3.0 DEPRECATED FUNCTIONALITY |