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

RE: Subversion roll-out strategy questions?

From: <jason_at_subversus.org>
Date: 2006-06-22 18:11:02 CEST

Well, if you haven't already read them, there's no better place to start


And assuming you want to use TortoiseSVN for your Windows systems:


Both are excellent references for Subversion (the first being more generic,
the second being more focused on TSVN, but still providing some additional

Fumbling along on something is seldom the best approach, especially with
something as complex as version control. IMO, you should come up with some
plan to set up SVN server / clients, a plan to structure your SVN
repository/repositories, a plan to import that data into that structure, and
a plan to train your initial users to use the system. This requires some
effort initially by at least one "point of contact individual" to ensure a
smooth transition, but in the long run I think you'll make fewer mistakes
and be happier overall with your experience. And then along the way this
mailing list (and especially the archive) will answer questions that arise.

-----Original Message-----
From: Matt Vance [mailto:mvance@pobox.com]
Sent: Thursday, June 22, 2006 11:33 AM
To: users@subversion.tigris.org
Subject: Subversion roll-out strategy questions?

I work on a team of web developers and designers for a university and we
would like to implement Subversion on our testing server. While we all
recognize the need for some kind of version control, none of us have
much experience in the area. I think that everyone is a little hesitant
to get started because we don't want to get things wrong from the outset
and saddle ourselves with a screwed up implementation.

Our testing server is a Red Hat box which we access primarily via Samba
shares. Our sysadmin has installed Subversion for us, but he has little
experience with it either, so nothing has been added to it yet. We use
mostly PCs, with the occasional Mac. Our files are primarily html,
graphics, and some php.

Should we just dive in head first by adding everything into Subversion
and fumble our way along? Or is there some easier way to gradually get
everyone up to speed? I'm open to any suggestions, advice, or pointers.
Will Subversion be easy enough for our part-time student workers to be
able to handle without screwing things up?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 22 18:15:14 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.