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
Received on Fri Jun 23 03:05:57 2006