Re: Branching suggestions needed...

[Todd Denniston]

James Depaul wrote:
> > > My initial impression of your system was Branch Aholic[2], but it looks
> like you
> are planning to branch at "release" points, which is normally a good place
> to
> put a branch. <<
>
> I see now that we'll end up with LOTS of branches that may or may NOT be
> used at all - depending on wheather or not they will require fixes.
> Questions:
>
> 1)  Is there a way to CLOSE a branch so as to prevent someone from
> mistakenly posting changes to the wrong /Branch?!

You may be able to get that with the cvs_acls script from the contrib 
directory (contrib directory in the source CVS tarball, or in 
/usr/share/cvs/contrib/ on most fedora boxes).


> 2)  What happens to those branches that are NEVER used for bug fixes - can
> they be purged somehow (or hidden) to avoid confusion?!

It may be possible to delete them, but it is highly recommended not to.
http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_System_v1.12.12.1:_Revisions#Deleting.2C_moving.2C_and_renaming_tags


> 3)  Would it make more sense to wait with Branching UNTIL there is
> something to fix, and only do TAGGING as means of marking specific
> mile-stones?!   What would work better here?

Yes. And with normal tags applied, if you later decide you need to branch at 
the point in time where the tag was applied, you can use the normal tag to 
make the branch.  Branches created in this manner look and act just exactly 
like they were created at the time of application of the normal tag.

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter