Changes between Version 1 and Version 2 of VersionNumbers
- Timestamp:
- 04/30/09 14:21:36 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
VersionNumbers
v1 v2 20 20 * 2010.4.1: minor bug fix release, compatible with 2010.4.0 21 21 22 == The general scheme == 23 24 $year . $major-release . $minor-version 25 26 Together, the $year and $major-release identify the major version. 27 28 When the $major-release is even, it's a stable release. Minor releases within a stable release are compatible. That is, programs that worked with 2010.2.0 or 2010.2.1 will still work with 2010.2.2. (Note, we have not decided if programs that work with later minor releases should also work with earlier ones, ie can minor releases add new APIs. This policy question has to be resolved by the libraries list.) 29 30 When the $major-release is odd, it's a testing pre-release. Minor releases are fresh testing snapshots. There is no API compatability guarantee. 31 22 32 == Rationale == 23 33 … … 29 39 30 40 Q: Are pre-releases API compatible with the final release? 31 A: No, there is no such guarantee for testing pre-releases. Only minor stable releases are guaranteed to be API compatible with the previous minor releases in the same major release series. That is, programs that worked with 2010.2.0 or 2010.2.1 will still work with 2010.2.2.In practice we expect there to be an API freese some weeks before the major release, so that testers have time to check the whole thing works without there being constant API churn.41 A: No, there is no such guarantee for testing pre-releases. Only minor stable releases are guaranteed to be API compatible with the previous minor releases in the same major release series. In practice we expect there to be an API freese some weeks before the major release, so that testers have time to check the whole thing works without there being constant API churn. 32 42 33 43 Q: Should the pre-release for 2010.2.0 be called 2010.1.x even if it's still 2009?
