Changes between Version 2 and Version 3 of VersioningPolicy


Ignore:
Timestamp:
08/26/10 11:31:48 (4 years ago)
Author:
dread
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VersioningPolicy

    v2 v3  
    99Note, changes go into the `default` branch, but the version number stays the same. 
    1010 
    11 Bugfixes may appear on branches, yet by default, the code will also keep the same version number. That is unless we decided that the fix is useful to advertise, and therefore released as a point release. Then the version number on `default` is upped (e.g. to `1.2.1`), and the same change made on other branches that have the fix. ''Note'', because `default` may have other changesets since the release unrelated to the fix, we ''can't merge'' from `default` to the branches for either the bugfix or the version number change - instead use `hg import` and `hg export`. 
     11Bugfixes may appear on branches, yet by default, the code will also keep the same version number. That is unless we decided that the fix is useful to advertise, and therefore released as a point release. Then the version number on `default` is upped (e.g. to `1.2.1`), and the same change made on other branches that have the fix. ''Note'', because `default` may have other changesets since the release unrelated to the fix, we ''can't merge'' from `default` to the branches for either the bugfix or the version number change - instead use `hg import` and `hg export` (or extension `hg transplant`).