On 3/15/07, Robert Denton <email@example.com> wrote:
> Hi all,
> I am hoping someone here can advise me on how best to implement
> autoversioning for my environment. The best thing you could do for me
> immediately is point me to a really informative read discussing
> subversion/webdav/autoversioning/windows clients, et al.
> Any good links you can recommend? I have looked through the nightly
> red bean book, and it is a good start, but I want to read more in
> depth before I delve too much deeper...
> What I am looking at is basically this:
> We run subversion 1.3 on a windows/apache server and we have limited
> it's availability to the techies in our company. We now have decided
> to move the entire company away from VSS to this. The problem is that
> the rest of the company is decidedly NOT tech savvy so we need a way
> for them to use subversion without getting flustered or confused, or
> breaking our repo.
> Currently the techs use TortoiseSVN. We were hoping for something a
> little more seemless. We enforce locking on all files, including
> text, doc, etc, so whatever solution I go with needs to be able to
> lock a file automatically and unlock and commit the file
> automatically, as well as make sure that the user isn't looking at a
> non-updated collection of files.
Are you certain that you can't distribute TSVN? Can you pilot it with
a few "regular" users and see if maybe you can avoid setting up
I considered autoversioning a long time ago, but in the end real log
messages from the committer won out (in addition to the other benefits
of using a regular client) over the little extra convenience that
autoversioning might have given me.
I have non-developers using TSVN and after a little time showing them
the basics, they're saying "ok, I get it now" and they're on their
way. They like that they can see history and they can work on their
files at home, disconnected from the network. They understand that
using it is good for everyone.
I have people in accounting and auditing departments asking me "can I
come to you in 4 months to get this set up for my whole department? We
*need* this and we'll gladly take these extra few steps to get all
this good functionality." They really like (among other things) that
they can see, right in TSVN, how much certain people are or aren't
using the system.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 16 03:17:35 2007