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

RE: A few questions

From: Alexander Johannesen <ajohanne_at_nla.gov.au>
Date: 2004-02-13 05:34:53 CET

From: Ben Collins-Sussman[SMTP:sussman@collab.net]
> It's a noble goal, but I think you're doomed to failure. :-)

Oh dear. :)

> You can't just "sneak" a version control
> system on developers when they're not looking, and hope they don't notice!

The developers are already using CVS, so no problems with them.

> As someone said earlier on this list: version control is a means to an
> end, not an end in itself. What overarching problems are you trying to
> solve in your company? Why do you think version control will help?

Basically it is a pre-phase before a CMS is in place for the intranet
and some websites. People have access to projects through Subversion,
do changes, and editors allow those changes out onto the production
servers, wherever they may be. Most people here can be trained to handle
versioning well, *except* a bunch of people that have limited access
to the projects tree.

> In other words, I think you need to move in the opposite direction:
> don't waste your time trying to make version control invisible. It's an
> impossible task. Instead, make it as visible as possible, and focus on
> educating people.

Can "somewhat invisible" be alright? :) All I need is for changes made to
projects go through editors before publication. A simple "commit to test,
commit to prod" cycle is all I need.

Anyways, thanks for the input. I'll have to ponder on this over the



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 13 05:35:31 2004

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.