| 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` |
| | 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` (or extension `hg transplant`). |
