Re: Branch creation takes a long time

Rick,

Look into user defined change sets ("cvs edit -b",
and "cvs ci -b" or
just "cvs cv -B").  This allows you to define a
change set without
needing to create a branch.

Creating branches for releases I personally think is OK -
particularly
if there is a high liklihood of needing to make changes down
the track.
Of course you can always just tag a release and then branch
when you
need to make that change.

In addition to Kelly's patch being in 2.5.04 we also have a
new project
"EVS" which uses a database backend rather than
RCS files, and creating
branches in that should be instantaneous.  The next test
release of that
should be out soon - but you should ask/check with the evs
newsgroup.
http://www.evscm.org/

Regards,


Arthur


-----Original Message-----
From: cvsnt-bouncescvsnt.org [mailto:cvsnt-bouncescvsnt.org] On Behalf
Of Rick Martin
Sent: Saturday, 7 April 2007 7:16 AM
To: cvsntcvsnt.org
Subject: Re: [cvsnt] Branch creation takes a long time


On Fri, 6 Apr 2007 14:15:31 -0300, Gerhard Fiedler wrote:

> Rick Martin wrote:
> 
>> Don't want to steal the OP thread, but what would
you consider to be 
>> a LOT fo branches? I work for a manufactoring
company and due to the 
>> software design we do an official release every two
weeks to the 
>> factory floor. I'm creating a branch for each of
these and then 
>> creating a tag if we need to release a bug fix on
the build branch. 
>> This creates a fair number of branches and tags.
Too many?
> 
> I'm not sure I understand your procedure correctly, but
couldn't you 
> tag these official releases, and only branch this tag
later if you 
> actually need to do some bug fixing? Assuming that
fixing bugs in an 
> official release is the exception rather than the rule,
this would cut

> down quite a bit on the number of branches.
> 
> Gerhard

Hi Gerhard,

Yes, we can set a tag. In fact I do so we can see the
starting point of
the branch easily. However, it's not just bug fixes. The
design of the
software requires coding changes for things that really
shouldn't be in
code (don't even get me started on that topic). So most
releases have
partial updates before the next release. Hopefully, some
redesign work
will get done and we can reduce the partial releases.

Thanks,
Rick
_______________________________________________
cvsnt mailing list
cvsntcvsnt.org h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
cvsnt mailing list
cvsntcvsnt.org
h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt