Just a question for Chris, from a green subversioner:
Why do you fell necessary to tag trunk-to-dev_v1 AND dev_v1-to-trunk? How
does it make it easier to merge between dev_v1 and trunk?
Regards,
Ignacio González
--------------------------------------------------
El 4 Dec 2006 a las 16:28, Chris.Fouts@qimonda.com escribió:
Date sent: Mon, 4 Dec 2006 16:28:57 +0100
From: <Chris.Fouts@qimonda.com>
To: <users@subversion.tigris.org>
Subject: RE: Subversion's repositories
I have a couple of suggestions.
First off, set your repository structure "outside" of Subversion, and then "svn
import" it. With this approach, adding and deleting dirs/files is easier since you do
NOT have to deal with Subversion yet.
Second, there are 1001 different ways to do the dir structure, but I suggest the
following; I'm assuming that priject1, project2, are NOT related
svn_root
project1
trunk
web
job
branches
dev
v1
web
job
v2
web
job
qa
v1
web
job
v2
web
job
tags
project2
(same fundamental structure as for project1)
I'm ONLY suggesting the structure because this facilitates "logical" branching
and tagging. For example, for branching
- You set up your trunk structure first
- Then you "svn copy" your trunk structure to your branch structure
> svn mkdir //svn_root/project1/branches/dev
> svn mkdir //svn_root/project1/branches/qa
> svn cp //svn_root/project1/trunk //svn_root/project1/branches/dev/v1
> svn cp //svn_root/project1/trunk //svn_root/project1/branches/qa/v1
- Create tags to facilitate merging between trunks and branches, both
on the trunk and the branches, as soon as you create the branches
> svn cp //svn_root/project1/trunk //svn_root/project1/tags/trunk-to-dev_v1
> svn cp //svn_root/project1/branches/dev/v1 //svn_root/project1/tags/dev_v1-to-
trunk
> (similar for qa branch)
Like I said, this is just "a" way to do it, and not necessarily "the" way.
From: T. Nguyen [mailto:ptn_y2k1@yahoo.com]
Sent: Sunday, December 03, 2006 12:40 AM
To: users@subversion.tigris.org
Subject: Subversion's repositories
Hi,
I am setting up a Subversion server. As I read several books and searched
on the internet, I have not seen any complicatedrepository structure as my
workplace requested. Please see thefollowing structure:
svn_root
dev
project1_root
project1_web
project1_web_v1
trunk
tags
branches
project1_web_v2
(trunk, tags, branches)
project1_jobs
project1_jobs_v1
(trunk, tags, branches)
project1_jobs_v2
(trunk, tags, branches)
project2_root
.....
.......
.......
........
project3_root
qa
................(same structure as dev)
Here are my questions that I need your helps.
1. Is it possible to have that kind of structure in Subversion? If yes, is it a
good or bad structure? And is it easy to maintain later? If no, please give
me your advise what I should do?
2. If it's possible, whichlevel should I use 'svnadmin create' and whichlevel
should I use'svn mkdir'?
I am looking forward to receiving your response. Thank you very much.
Regards,
Tracy
Received on Tue Dec 5 09:02:00 2006