The current stable release is 1.0.1, released 7 September 2008.
The latest release is 1.0.1, released 7 September 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 on no notice.
| Date | Type | Name | Comments |
|---|---|---|---|
| 13-Sep-2008 | checkpoint | 1.0.1.d20080913 | Beta for 1.1. Prioritization of work items and checkins for 1.1 are occuring now. |
| 27-Sep-2008 | candidate | 1.0.1.d20080927 | Release candidate for 1.1. |
| 4-Oct-2008 | release | 1.1 | First minor release of 1.0. |
| 11-Oct-2008 | checkpoint | 1.1.d20081011 | Beta for testing new features. |
| 25-Oct-2008 | checkpoint | 1.1.d20081025 | Beta for testing new features. |
| 8-Nov-2008 | checkpoint | 1.1.d20081108 | Beta for testing new features. |
| 15-Nov-2008 | candidate | 1.1.d20081115 | Release candidate for 1.2. |
| 22-Nov-2008 | release | 1.2 | Second minor release of 1.0. |
| 29-Nov-2008 | checkpoint | 1.2.d20081129 | Beta for testing new features. |
| 13-Dec-2008 | checkpoint | 1.2.d20081213 | Beta for testing new features. |
| 27-Dec-2008 | checkpoint | 1.2.d20081227 | Beta for testing new features. |
| 3-Jan-2009 | candidate | 1.2.d20090103 | Release candidate for 1.3. |
| 10-Jan-2009 | release | 1.3 | Third minor release of 1.0. |
| 17-Jan-2009 | checkpoint | 1.3.d20090117 | Beta for testing new featurea; breaks backward compatibility with Python 1.5.2. |
| 24-Jan-2009 | checkpoint | 1.3.d20090124 | Beta for testing new features. |
| 31-Jan-2009 | candidate | 1.3.d20090131 | Release candidate for 2.0. |
| 7-Feb-2009 | candidate | 1.3.d20090207 | Release candidate for 2.0, if needed. |
| 14-Feb-2009 | release | 2.0 | Public release that breaks backward compatibility |
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.
Minor numbers increment for releases that add new functionality and/or bug fixes to an existing major release. All new functionality will be added so as to never knowingly break backwards compatibility with any previous minor releases from the same major release. We expect that our major releases will be long-lived platforms for delivering many minor releases to add functionality and fix bugs.
Revision numbers are appended and/or incremented whenever a critical bug fix is necessary for a major or minor release. Bedause 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 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 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 urgently need to use the feature in advance of it being published in the next major or minor release. Checkpoints can also act as release candidates immediately prior to a major or minor release.