[torquedev] Versioning Issues & Development Roadmap

Glen Beane glen.beane at gmail.com
Thu May 28 21:37:06 MDT 2009


On Thu, May 28, 2009 at 11:29 PM, Garrick <garrick at usc.edu> wrote:
> There's nothing wrong with the versioning scheme, just stop adding
> features to "fixes" branches and do all development in trunk. Fixes
> are always backported from trunk down to all supported branches. As
> long as changes in trunk are backwards compat, then new releases keep
> the same major number.  Easy.
>
> Current trunk should stay on track as 2.4.


There are cases where you want to be able to be working on the next
minor release and the next major release at the same time.  A major
release could be a long-term project, during which several minor
releases may happen (with bug fixes and minor features back ported
from the major version in development).  If it is going to take you a
year to make some major change you don't want to put a halt to minor
version releases.


More information about the torquedev mailing list