Re: Branching models

Thanks Jim,

It's good to know I'm not alone in this matter. I'm still concerned about
subversion behavior in the long run. I have no idea if branching 15,000
files, 7 times per day will let my repository slower after two or three
years of development. I already know that it's not a good idea to do this
with CVSNT.

Can subversion cheap copies cope with all this branching without loosing
(too much) performance?

Maybe someone from the dev team can make things clear?

Thanks in advance.
Daniel

----- Original Message -----
From: "Jim Nutt" <jim@nuttz.org>
To: <users@subversion.tigris.org>
Sent: Thursday, March 04, 2004 7:18 PM
Subject: Re: Branching models

On Thu, 4 Mar 2004 18:56:41 -0300
"Luiz Daniel Lapolla" <luiz.lapolla@sfw.com.br> wrote:

> We are considering the adoption of a branch-by-task model:
> - A new branch (across all files) is created for each Change
> Request,
> based on the last stable milestone.
> - All the development for one CR goes on it's own branch.
> - After N cicles of testing and bugfixing the branch is scheduled
> to be
> merged with it's baseline.

This is the development model we're currently using. Performance seems
to be good, but we've not really been using SVN long enough to get solid
numbers.

One caveat is that merging the whole branch back is a bit different than
in CVS (you have to specify the starting revision of the branch). It's
not that it's any more difficult, it's just that it's different enough
that it's easy to make mistakes until you get the hang of it (the first
few times I did it nearly drove me to distraction). Once you get used
to it it though, it's not any harder than under CVS and has some
advantages.

-- 
jim nutt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org