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

Re: Recommended Subversion Development Setup

From: Brooke Smith <novorivus_at_optusnet.com.au>
Date: 2004-10-09 07:03:47 CEST

Hi Chris,

1. I don't believe you can do operations between repositories so you
would want to have just the one repository with dev, test and prod root
directories (however, see below).
2. The most common (recommended) repository structure has 'trunk',
'branch' and 'tags' sub-directories under projects. In our repository
configuration, we want to maintain versions of each project so our
structure looks like this:
   <project 1>/
          /trunk/
          /branch/
                 /<branch name 1>
                 /<branch name 2>
                 /...
          /tags/
               /<tag / label 1>
               /<tag / label 2>
               /...
   <project 2>/
            /...

trunk - main line of development
branch - bug fixes on past versions or area for development to be done
separately to the trunk
tags - keep versions in here (copy from the trunk or branches).
Release the code from here as versions.

As for your 'test' and 'prod' directories, I'm expecting that you don't
actually develop in these but rather you use these to do testing and
for your production code. In which case these will live outside of the
repository and the repository will only contain your development
environment. You will do an

svn export <project>/trunk or
svn export <project>/tags/<tag X>

into your test and prod environments (or just export to test and when
the tests pass then copy to your prod environment - though its a lot
cleaner if your process is to only get code by exporting it from the
repository).

I hope that helps!

Cheers,

Brooke

On Saturday, Oct 9, 2004, at 09:28 Australia/Brisbane, Chris Jacoby
wrote:

> I am new to Subversion and am looking for a "best practice" setup of my
> repository(ies)? for my application team. Our current coding structure
> practices fall under large project names and then they are broken down
> into development, test, and production, maintenance, etc environments.
> Should each environment be its own repository and contain the branches,
> trunk, and tags directories. Or should I define a root repository that
> contains all of the environments for a specific project. I know this
> is
> not an exact science, I was just looking for ideas. Version control
> will be a new concept to my application team and I want to introduce it
> to them as simply as possible to ensure they do not fight it.
>
> Here are a couple of common project layouts
>
> <project>
> <test>
> code1
> code2
> code3
> <development>
> code1
> code2
> code2a
> code2b
> code3
>
> I am looking forward to implementing the repository to remove the need
> for different versions a single program (as in the development example
> above). Any help would be appreciated.
>
> Chris Jacoby
> chris.jacoby@ers.state.tx.us
> 512.867.7118
> ERS of Texas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---
You picked a fine time to leave me Lucele,
four hungry kids and a crop in the field.
-- Kenny Rogers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 9 07:26:59 2004

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.