Managing CVS

[Ruslan Zasukhin]

On 24/4/07 12:44 AM, "Robert Brenstein" <rjb at robelko.com> wrote:

>>> And yes, being able to release 2.5.10 after 3.0 should be not just
>>>  possible but easy if you do things right :-)
>> 
>> Yes, "as easy" as above steps, Robert.
> 
> Well, let's agree that we disagree. If you fix problems in the head,
> then yes, indeed fixing earlier branches is a headache. Fixing should
> be done in the oldest active branch, so CVS tools can be used to
> merge them up into the newer branches and the head. That works
> simpler.

I wonder, does your project team have some instructions how to manage CVS in
that project? If yes, will be happy to read exact steps.

We have try already few ways actually:
    e.g. 2.5 was main branch, and 3.0 was separate secondary.

now we have change this
    3.0 is in head, and e.g. 2.5.10 we can make as I did describe
    following to what I have read about "how to make bug-fix build"
articles.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]