[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RE: RE: Re: Repositories organization

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-10-02 15:09:18 CEST

> -----Original Message-----
> From: Gonzalez Diaz, Xoan [mailto:G2485@caixagalicia.es]

> releases. So here comes the unusual ... To avoid using merges and
> manually review conflicts ... we rename trunk as trunk_old, make
> a copy of the appropiate tag to trunk and delete trunk_old.
> 5. In this way we can recover to any release version easily
> without any human intervention and without loosing history.
>
> I am thinking if would be a space problem ... Any thoughs?
> Disadvantages?? Am I completely fool? Help me to avoid
> psychiatrist! :)
>
> Thanks,
>
> xoan
>

That sounds similar to the "branch by release" model. I attached a PDF
I found on the internet (I don't know if it will be filtered out) that
describes branching models and explains reasons why the one prefered by
Subversion developers and power users (branch by purpose) is usually the
easiest to handle. I want to say "best", because I do feel it is, but
that is a subjective opinion.

I also included a "talkback" document I found more recently, which
contains reader comments on the original article, including a defense of
"branch by release". I think there are disadvantages to what you wish
to do both in organization and ease of tracing back in time. These are
covered in the attached documents.

I just did a quick google and found this PDF is available at
(www.accurev.com/product/docs/SCMBranchingModels1.pdf) in case it is
filtered out of my post.

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************



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

Received on Wed Oct 3 01:57:38 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.