Changes between Version 1 and Version 2 of VersionNumbers

Show
Ignore:
Timestamp:
04/30/09 14:21:36 (6 years ago)
Author:
duncan (IP: 79.70.231.184)
Comment:

section on the general scheme

Legend:

Unmodified
Added
Removed
Modified
  • VersionNumbers

    v1 v2  
    2020 * 2010.4.1: minor bug fix release, compatible with 2010.4.0 
    2121 
     22== The general scheme == 
     23 
     24$year . $major-release . $minor-version 
     25 
     26Together, the $year and $major-release identify the major version. 
     27 
     28When 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 
     30When the $major-release is odd, it's a testing pre-release. Minor releases are fresh testing snapshots. There is no API compatability guarantee. 
     31 
    2232== Rationale == 
    2333 
     
    2939 
    3040Q: 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. 
     41A: 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. 
    3242 
    3343Q: Should the pre-release for 2010.2.0 be called 2010.1.x even if it's still 2009?