Methodology for Source Code Control

[Peter Ring]

It is not quite clear what your problem is.

Branches are for lines of development, i.e. parallel development of 
variants with a common ancestor and some need to merge changes between 
branches and trunk. Is that what you have to do?

Maybe you just want an easy way to retrieve the set of revisions that is 
related to a specific release. You don't need branches for that, just a 
'release' tag or a date. You can branch at that release point later if 
you need.

If you don't have release tags yet, you can easily tag (or retrieve) the 
set of revisions at a specific date and time.

There is a description of cvs branches, what they are good for, and some 
advice on practices in the cvs documentation. See the section 'Branching 
and merging'.

See also 'Open Source Development with CVS', Chapter 6 'Going Out On A 
Limb', http://cvsbook.red-bean.com/cvsbook.htm.

Kind regards
Peter Ring

karyn hunt wrote:
> Hi Guys,
> 
>   I know this is somewhat off topic, but perhaps the responses will be 
> helpful for others. I've been checking my FrameMaker files in to CVS for 
> source control purposes and just felt the sting of not having used 
> branches. In other words, I've always checked my FrameMaker files right 
> in to the head and overwritten them with each new release. Until this 
> week, that wasn't a problem. But this week, I began to see the 
> shortcomings of that system.
> 
>   So I'm wondering, how many of you out there use branching when 
> checking your Frame files in to a source code control system and how 
> many of you just overwrite in one place?
> 
> Karyn Hunt
> 
> 
> _______________________________________________
> 
> 
> You are currently subscribed to Framers as pri at ddf.dk.
> 
> Send list messages to framers at lists.frameusers.com.
> 
> To unsubscribe send a blank email to 
> framers-unsubscribe at lists.frameusers.com
> or visit http://lists.frameusers.com/mailman/options/framers/pri%40ddf.dk
> 
> Send administrative questions to lisa at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
>