| View previous topic :: View next topic |
| Author |
Message |
pbean
n00b
Joined: 28 Apr 2009
Posts: 4
|
 Posted: Tue Apr 28, 2009 6:14 am Post subject: Subversion repository layout with multiple projects? |
 |
|
When having multiple projects in one repository, what is the recommended layout?
This:
| Code: | /trunk/project1
/trunk/project2
/trunk/project3
/tags/project1
/tags/project2
/tags/project3
/branches/project1
/branches/project2
/branches/project3 |
Or this:
| Code: | /project1/trunk
/project1/tags
/project1/branches
/project2/trunk
/project2/tags
/project2/branches
/project3/trunk
/project3/tags
/project3/branches |
|
|
| Back to top |
|
 |
ToeiRei
Veteran
Joined: 03 Jan 2005
Posts: 1191
Location: Austria
|
| Posted: Tue Apr 28, 2009 6:27 am Post subject: |
|
|
if you'd ask me it's the 2nd one as you seperate the projects in a logical way.
_________________
Please stand by - The mailer daemon is busy burning your messages in hell... |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
bartlm
n00b
Joined: 15 Aug 2008
Posts: 15
Location: Fürstenzell
|
| Posted: Tue Apr 28, 2009 1:22 pm Post subject: |
|
|
Whatever you prefer...
My way is the first one  |
|
| Back to top |
|
|
pbean
n00b
Joined: 28 Apr 2009
Posts: 4
|
| Posted: Tue Apr 28, 2009 5:28 pm Post subject: |
|
|
| bartlm wrote: | | Whatever you prefer... |
Well obviously that's true... I could also go crazy and invent my own layout, but that's not really handy imho as there are already established standards and recommendations.
| UberLord wrote: | | I personally have one repo per project, but if forced I'd choose the second one. |
I would normally just create one repo per project as well, in fact I do this already do this for my bigger projects. However I now have a situation where I have multiple smaller projects which are very much related, and it would be tedious to create a repo for each of them separately and manage the authentication for them as well. This case is regarding small web sites for various clients using a common system and set-up, with a new project every one or two weeks. |
|
| Back to top |
|
|
timeBandit
Bodhisattva
Joined: 31 Dec 2004
Posts: 2719
Location: here, there or in transit
|
| Posted: Tue Apr 28, 2009 7:19 pm Post subject: |
|
|
| pbean wrote: | | I could also go crazy and invent my own layout, but that's not really handy imho as there are already established standards and recommendations. |
Standards, not so much; recommendations aplenty.
| Quote: | | I now have a situation where I have multiple smaller projects which are very much related, and it would be tedious to create a repo for each of them separately and manage the authentication for them as well. This case is regarding small web sites for various clients using a common system and set-up, with a new project every one or two weeks. |
Which layout you prefer should depend on how independent your projects are. When they all tend to follow their own timelines and development plans, without regard for each other, the second layout makes more sense. The first is more logical when the projects are organizational units of a larger effort and tend to be planned and released together (or nearly so).
FWIW, I use the second layout.
_________________
Plants are pithy, brooks tend to babble--I'm content to lie between them.
Super-short f.g.o checklist: Search first, strip comments, mark solved, help others. |
|
| Back to top |
|
|
|
Networking & Security
