On Oct 23, 2007, at 9:10 PM, Blair Zajac wrote:
> As somebody who runs an svn server for open source code and one for
> internal corporate use, I want to ensure that all svn clients that
> commit send merge info to the server and I don't want to loose this
> information. So I want to require that all clients that commit are
> at least Subversion 1.5 or later. I can imagine that lots of
> corporate shops will want this requirement to prevent somebody from
> using some random svn client that does not supply merge info and
> makes life harder for a release manager.
>
> Are we planning on offering such a capability? If so, how are we
> doing this? If not, this seems like a good use for the start-
> commit script to supply an additional parameter, say an $OPTIONS,
> that can be parsed for the support the client offers.
It has just occurred to me that we spent a lot of time on this list
deciding to allow mixing 1.4 and 1.5 clients within a single working
copy (so users could mix clients on a single client box), but with
this thread we've dashed clear to the opposite extreme: we now
require *all* clients on every box on the planet to upgrade to 1.5
before we can upgrade the server. These are not quite contradictory
positions, in that you can still imagine a careful management of the
environment that satisfies the constraints ... but both these
discussions were all about doubts that the environment would be
carefully managed, so that doesn't seem like a way out.
Is this near-contradiction really desirable?
-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 26 13:07:33 2007