jay,
If your developers are content with VSS, and if the budget decisions
can/will handle VSS, what's the issue? If the developers as a group object
to working with a tool, you're going to have issues getting them to work
with it.
In all honesty, you shouldn't 'force' them to have to use SVN if they where
already using VSS. However, if you guys weren't using VSS, and the
developers simply want to use something that's similar to what they were
using at some other prior company, then they should be willing to
adjust/recognize the differences, and move on.
Since I'm obviously not aware of all the underlying nuances/issues of your
situtation, I wish you well!!!
-Bruce
-----Original Message-----
From: jzorzi@marketlinksolutions.com [mailto:jzorzi@marketlinksolutions.com]
Sent: Tuesday, April 05, 2005 6:42 AM
To: users@subversion.tigris.org
Subject: Development Process
Is there a good reference guide or best practices guide for developing web
based applications under subversion?
I'm trying to convince the developers in our organization to use subversion
but they are resistant to the change in paradigm from VSS. They keep asking
me to write scripts to make Subversion act more like VSS. I would like some
programming strategies for web development to show them and prove to them
that the switch to subversion requires a change in mind set.
Thanks in advance
Jay Zorzi
Systems Administrator, Information Technology
MarketLink Solutions
see further. achieve more.
e - jzorzi@marketlinksolutions.com
t - 416.260.2800 x299
f - 416.260.2893
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 5 16:07:18 2005