The current stable release is 1.0.1, released 7 September 2008.
The latest release is 1.0.1.d20081001, released 2 OCtober 2008.
Our goal is to meet the dates for release candidates and the releases themselves; the beta checkpoint dates are our best guess as this was published, but they may be adjusted without notice.
| Estimated date | Type | Comments |
|---|---|---|
| 13-Oct-2008 | Ckpt | Beta for testing new features. |
| 27-Oct-2008 | Ckpt | Beta for testing new features. |
| 10-Nov-2008 | Ckpt | Beta for testing new features. |
| 17-Nov-2008 | RC | Release candidate for 1.2. |
| 24-Nov-2008 | 1.2 | Second minor release of 1.0. |
| 1-Dec-2008 | Ckpt | Beta for testing new features. |
| 15-Dec-2008 | Ckpt | Beta for testing new features. |
| 29-Dec-2008 | Ckpt | Beta for testing new features. |
| 5-Jan-2009 | RC | Release candidate for 1.3. |
| 12-Jan-2009 | 1.3 | Third minor release of 1.0. |
| 19-Jan-2009 | Ckpt | Beta for testing new features; breaks backward compatibility with Python 1.5.2. |
| 26-Jan-2009 | Ckpt | Beta for testing new features. |
| 2-Feb-2009 | RC | Release candidate for 2.0. |
| 9-Feb-2009 | RC | Release candidate for 2.0, if needed. |
| 16-Feb-2009 | 2.0 | Public release that breaks backward compatibility and drops deprecated features |
Our release numbers are of the form major.minor.revision.
The major number increments when one of two things happens:
Our goal is that as a user of SCons, you should always be able to upgrade to a later release of the same major version with complete confidence that your build will not break. We expect that our major releases will be long-lived platforms with many minor releases to add functionality and fix bugs.
Minor numbers increment for releases that add new functionality and/or bug fixes to an existing major release. Any new functionality will never knowingly break backwards compatibility with any previous minor releases from the same major release.
Revision numbers are appended and/or incremented whenever a critical bug fix is necessary for a major or minor release. Because most new functionality and bug fixes will be delivered in minor releases, we expect that there will be few of these—at most one per minor release.
A release candidates is a special form of checkpoint (see below) that is expected to be the next major or minor release. If blocking issues show up in the candidate, another candidate will normally be issued (potentially delaying the release date), otherwise the candidate will be repackaged as the major or minor release.
A checkpoint has a 'dyyymmdd' suffix and is made every couple of weeks between major or minor releases. It is intended for beta testing new features and for ensuring that bug fixes work as intended. Although existing features from the previous release will not change, compatibility of features under test is not guaranteed between checkpoints (i.e., the implementation of the feature may change). Checkpoints are intended not only to allow for wider testing, but also to make new features available to users (who may urgently need one of them) in advance of them being published in the next major or minor release.