I've tagged the latest release of CamelBones as 'release-0_2_2', and
it's time to create a CVS branch.
There appear to be two major schools of thought concerning branches -
one where most active development takes place in the trunk, and one
where most active development takes place in branches.
I'm leaning towards the "active trunk" philosophy, meaning that I'm
thinking of creating a stable-0-2 branch which will be limited to bug
fixes and minor additions only. Ongoing development, including however
many 0.3-series releases are made, would happen in the trunk. I'm also
thinking of adopting the popular even/odd versioning like Perl uses, so
once 0.3 reaches stablity, a stable-0-4 (or stable-1-0) branch would
then be created for ongoing maintenance of that version, and the
I'm a fairly new CVS user, though, so I'd like to get some input before
proceeding. Does this sound like a plan y'all can live with? Does
anyone have CVS success and/or horror stories to share?
On Mar 2, 2004, at 1:10 PM, Sherm Pendley wrote:
> I've tagged the latest release of CamelBones as 'release-0_2_2', and
> it's time to create a CVS branch.
No one screamed "for the love of $DEITY, don't do that", so I've
created the branch. The 'maint-0-2' branch is where bug-fixes and
whatever additions are appropriate to 0.2.x will get checked in. The
trunk is where new development - what will be 0.3.x - is happening.