Versioning
cnorthwood edited this page Mar 30, 2011
·
2 revisions
Below we describe the versioning scheme
Major.Minor.Release
Major Version releases come with substantial, potentially non-backwards-compatible changes, typically with major functionality improvements.
Bugfixes and large pieces of new functionality. Although some work may be required to bring a deployment up-to-date with changes, there should be no major work done by users.
These are bugfixes only (or very minor functionality changes) that should maintain compatibility with any deployments with no, or very small, changes.
Like so: 1.0dev8d, 1.6b1, etc. Used to denote release candidates/betas/etc
Like so: 1.0-5, but we should try and avoid these and do a new release
- Changelog-1.4.5
- Changelog-1.4.4
- Changelog-1.4.3
- Changelog-1.4.2
- Changelog-1.4.1
- Changelog-1.4
- Changelog-1.3.4
- Changelog-1.3.3
- Changelog-1.3.2
- Changelog-1.3.1
- Changelog-1.3
- Changelog-1.2.3
- Changelog-1.2.2
- Changelog-1.2.1
- Changelog-1.2
- Changelog-1.1.2
- Changelog-1.1.1
- Changelog-1.1
- Changelog-1.0
- Changelog-0.5.1
- Changelog-0.5
- Changelog-0.4