You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Matt Vance <mv...@pobox.com> on 2006/06/22 15:32:42 UTC
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?
Thanks,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Subversion roll-out strategy questions?
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Matt Vance wrote:
> 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?
Do a sample project: for example, start with an internal web page or other
modest project. This gets you a chance to learn about authentication,
backup, etc. and how to merge it into your environment.
Also note that the 64-bit use of Subversion, at least via RPM installation,
requires a modest patch to David Summers published SRPM's.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Subversion roll-out strategy questions?
Posted by Res Pons <po...@hotmail.com>.
Luckily when I installed SVN on a Linux RHEL3.5 server I ran into no
problems! Beginner's luck? :)
I dowloaded the latest for rhle3.5 and installed them in the following order
as root or sudo:
1. sudo rpm -i neon-0.24.7-1.i386.rpm (or latest)
2. sudo rpm -i subversion-LATEST-stable-version.rhel.i386.rpm
3. sudo rpm -i mod-dav-svn-LATEST-stable-version.rhel.i386.rpm
4. sudo rpm -i subversion-tools-LATEST-stable-version.rhel.i386.rpm
5. sudo rpm -i swig~.rpm (if you're going to install perl or python
bindings)
6. sudo rpm -i perl or pythom.rhel*.rpm
if no error msgs...then type svn at the prompt to see the svn get help
reply. Then I created my repo, imported my project from cvs, set up apache,
my admin files, email notifications, etc.
The installation and set up took me about an hour but the killer was the
cvs2svn conversion that took about 15 hrs.
Good luck :)
----Original Message Follows----
From: Matt Vance <mv...@pobox.com>
To: users@subversion.tigris.org
Subject: Subversion roll-out strategy questions?
Date: Thu, 22 Jun 2006 10:32:42 -0500
MIME-Version: 1.0
Received: from tigris.org ([204.16.104.146]) by bay0-mc5-f8.bay0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.2444); Thu, 22 Jun 2006 09:48:48 -0700
Received: (qmail 6280 invoked by uid 5000); 22 Jun 2006 15:56:24 -0000
Received: (qmail 29262 invoked from network); 22 Jun 2006 15:32:47 -0000
X-Message-Info: LsUYwwHHNt0B1wvFlySfeBhyPXxPtrza/GcV7PyvGmk=
Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
Precedence: bulk
list-help: <ma...@subversion.tigris.org>
list-unsubscribe: <ma...@subversion.tigris.org>
list-post: <ma...@subversion.tigris.org>
Delivered-To: mailing list users@subversion.tigris.org
Delivered-To: moderator for users@subversion.tigris.org
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AQAAADhUmkSKAgcECCw
X-IronPort-AV: i="4.06,166,1149490800"; d="scan'208";
a="23235105:sNHT16694811"
X-IRONPORT: SCANNED
X-Sasl-enc: aw/CGRPGgiOJ2xkwsC81L8EODgiUELT3QAUpuuLsTvyq 1150990367
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
Return-Path: users-return-50877-pons32=hotmail.com@subversion.tigris.org
X-OriginalArrivalTime: 22 Jun 2006 16:48:49.0142 (UTC)
FILETIME=[BC245960:01C6961B]
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?
Thanks,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar � get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Subversion roll-out strategy questions?
Posted by ja...@subversus.org.
Well, if you haven't already read them, there's no better place to start
than:
http://svnbook.red-bean.com/
And assuming you want to use TortoiseSVN for your Windows systems:
http://tortoisesvn.sourceforge.net/?q=support
Both are excellent references for Subversion (the first being more generic,
the second being more focused on TSVN, but still providing some additional
support).
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?
Thanks,
Matt
---------------------------------------------------------------------
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