Release Roadmap

Current Releases

The current stable release is 1.0.1, released 12 August 2008.

The latest release is 1.0.1, released 7 September 2008.

Upcoming Releases

Release	Est. Date?	Goals
1.0.1.d200809XX	23 September 2008	Candidate checkpoint release for 1.1.0.
1.1.0	30 September 2008	New features, bug fixes, documentation updates. Prioritization of work items and initial checkins are occuring now.
1.1.0.d200810XX	21 October 2008	Candidate checkpoint release for 1.1.1.
1.1.1	28 October 2008	Critical bug fixes for 1.1.0.
1.1.1.d200811XX	17 November 2008	Candidate checkpoint release for 1.2.0.
1.2.0	24 November 2008	New features, bug fixes, documentation updates.
1.2.0.d200812	15 December 2008	Candidate checkpoint release for 1.2.1.
1.2.1	24 November 2008	Critical bug fixes for 1.2.0.
2.0	19 January 2009 ???	First release that will break backwards compatibility with Python 1.5.2.

Release Planning

Release numbering

Our release numbers are of the form major.minor.revision.

• Major release (1.0, 2.0, 3.0, etc.)

  The major number increments when one of two things happens:

  • The release knowingly breaks backwards compatibility in some way.
  • The release knowingly causes a rebuild when you upgrade.
  Our goal is that as a user of SCons, you should always be able to upgrade to a later revision of the same major number with complete confidence that your build will not break.

• Minor release (1.1, 1.2, 1.3, etc.)

  Minor numbers increment for release that adds new functionality and/or bug fixes to an existing major release branch. All new functionality will be added so as to never knowingly break backwards compatibility with any previous minor releases from the same branch. We expect that our major release branches will be long-lived platforms for delivering many minor releases to add functionality and fix bugs.

• Bug-fix revisions (1.1.1, 1.1.2, 1.1.3, etc.)

  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.

• Testing pre-release (1.1.90, 1.1.91, 1.1.92, etc.)

  A revision number of 90 or greater indicates the release is intended for testing a set of new features intended for wider distribution in the next major or minor release. There may be many of these leading up to a release with a lot of significant internal changes (*cough* 0.97 *cough*...).