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
Received on Sat Oct 9 01:29:38 2004