I have been looking into using Subversion (namely
TortoiseSVN) on several projects and groups of files
that we have at work to track changes, diff versions,
etc. and to replace our manual (i.e. file system)
version control system.
However, Subversion seems to be geared toward each
developer having their own working copy and testing
their changes on their own machines, but because of
software license issues and the maintenance nightmare
it would take to do that we typically have a "test"
system, which holds our test code and pending changes
(with the appropriate licensed software), and a "live"
system, which holds the live code. So, we only really
have one "working copy." This single working copy
problem is not likely to change.... What I need,
though, is a workable, industry-standard version
control system.
Our current manual version control system is "copy the
original into this folder here before you edit it" but
I really want to get away from that.
I noticed that TortoiseSVN can add a "Lock" column to
Windows Explorer, and that could help multiple
developers working in a "single" copy from trampling
over each other, and the exclamation overlay icon also
helps us to see pending changes, but commits might
accidently put other programmer's code into
production....
Has anyone else had this problem, or could someone
point me in the right direction?
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Sep 7 08:06:15 2005