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

RE: cvs2svn project migration - structure of SVN repo

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-19 15:38:16 CET

> -----Original Message-----
> From: Martin Landa [mailto:landa.martin@gmail.com]
> I am cooperating on the migration of quite complicated CVS
> repo to SVN. Originally, the CVS repo contains two directories:
> grass5
> grass6
> grass6 HEAD is based on grass5 HEAD (grass6 has been created
> by copying the files from grass5 a few years ago). There is
> also another SVN repo called grass-addons. The goal is to put
> grass5, grass6 and grass-addons to the single SVN repo. Also
> new branch for future development called grass7 need to be
> created. This repo will be used together with Trac software.
> Basically I can see three different
> structures:

<diagrams removed>

> I guess solution 1) is badly designed. What about 2) and 3)?
> I will appreciate any hits, notes, suggestions, etc. If you
> are interested, more detailed information are available on
> wiki-page [1].
> Thanks a lot!

First, as requested, your hit: *THWAP* :D

I suggest you migrate grass5 as its own project. Presumably this one
will eventually be retired. Grass6 should be imported as "Grass" (no
version identifier in its name) into the trunk folder. If the grass
addons are dependent on grass, and won't be used for other projects, I'd
add the addons into trunk along with the rest of the project. If these
addons are a bit more generic, create a separate project for them.

When you're ready to begin work on Grass7, tag the trunk for Grass6,
create a branch for Grass7. Work on v7, and periodically merge to
trunk. Etc., so forth, and so on until the end of time (or you don't
need any more Grass (whoa, cool man!). Each new version is branched
from the trunk, which should be up to date with the prior version at the
moment of branching.

This method works best with teams and processes small enough to warrant
an "unstable trunk" technique. Things get more complicated from here,
and there are plenty of resource on the web.

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 Mon Nov 19 15:38:44 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.