summaryrefslogtreecommitdiff
path: root/src/RELEASE.txt
diff options
context:
space:
mode:
authorWilliam Deegan <bill@baddogconsulting.com>2017-06-14 11:45:17 -0400
committerWilliam Deegan <bill@baddogconsulting.com>2017-06-14 11:45:17 -0400
commit8b3b5443fed9eaf1a18def6e810281f85889d656 (patch)
treefa512e556ffb9a0b58121e7da36ecd4288e7edb7 /src/RELEASE.txt
parent5d171dea83e47bad5c6bc9e675cc02182f584f76 (diff)
downloadscons-8b3b5443fed9eaf1a18def6e810281f85889d656.tar.gz
updates for 3.0.0 alpha
Diffstat (limited to 'src/RELEASE.txt')
-rw-r--r--src/RELEASE.txt27
1 files changed, 2 insertions, 25 deletions
diff --git a/src/RELEASE.txt b/src/RELEASE.txt
index 07eaaf4d..f87f8894 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