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

autoversioning -- on or off by default?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-21 18:05:57 CET

cmpilato and I are having a bit of debate. We'd like opinions on this.

For a very long time, autoversioning (that is, the ability for generic
DAV clients to write to an svn repository) has been considered an
experimental feature. Mainly because it only half-worked... because we
had no locking support.

Now that locking support is real, so is the autoversioning feature.
The question is:

     When installing mod_dav_svn, should autoversioning be 'on' or 'off'
by default?

* cmpilato feels that one the original motivations for using
apache/HTTP/DAV was the long-term promise of being able to use generic
DAV clients against a repository. Therefore, as of svn 1.2, he thinks
autoversioning should be considered a "core feature" of mod_dav_svn,
and that it should be turned on by default.

* I'm still a bit recicent about that. I feel like opening a
repository to a bunch of DAV clients might lead to a lot of extra
commits, lots of extra noise in the commit logs. I feel like an
adminstrator should understand the implications of autoversioning, and
thus be forced to turn it on.

Do others on this list have strong opinions either way? We'd like to
hear them.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 21 18:07:12 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.