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

Help On Repository Setup and Use

From: Scott Wilfong <SCOTT_at_nikeaa.com>
Date: 2006-01-06 16:12:15 CET

I am relatively new to Subversion, so I was looking for advice on how the
following could be setup in Subversion. We currently work in Visual
SourceSafe, and are not totally satisfied with it. I want to have a plan all
laid out prior to possibly presenting a change to Subversion to management.


We have three separate areas where we work on our code:

Development – this is where we do our development work for the next
release (ex. V3)
QA – this is where the quality assurance department does their work on the
current release (ex. V2)
Production – this is the last production release (ex. V1)

The flow is as follows:

If there is a bug found in production, we fix it in production, then move
the code changes to the QA and Development versions.
If there is a bug found in the QA version, we fix it in QA and move the code
changes to the Development version.

When we are ready to release a new version of the software, we move the
version that is currently in QA to Production, the version in Development to
QA, and we start development work for the next release in Development. So
with the version numbers from above we now have V2 in Production, V3 in QA,
and we are starting work on V4 in Development.


What I need advice on is how to setup the repository and if and where
tags/branches should be used.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 6 16:15:34 2006

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.