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

Re: Auto Upgrade Behavior

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 27 Aug 2012 08:04:09 -0400

On 08/27/2012 07:56 AM, Stefan Sperling wrote:
> On Mon, Aug 27, 2012 at 04:47:58AM -0400, Greg Stein wrote:
>> I'm thinking that we ought to continue auto-upgrade for the masses,
>> especially given Bert's input. Much as I dislike config knobs, it seems
>> prudent to introduce a "disable auto-upgrade" option for large,
>> multi-client shops. IMO, you're tending towards sophisticated if you use
>> more than one svn client. In turn, I further believe that implies minority.
>> Let's give those users, who understand the issue, an option, and give
>> simplicity to all the rest.
>>
>> Would that work for you?
>
> Yes. This approach would benefit a lot from server-side configuration
> for deployment in large shops. Since server-side configuration is a
> targeted feature of some future release I could live with having
> troubled users edit their local configuration for the time being.

This is tending off-topic, but I'll note that this is in a class of
server-side configuration that would not (in fact, *should not* in my
opinion) be aided by the work that Paul is doing right now. Configuration
via inherited props is well suited for propagating behavioral preferences
that are more closely tied to the versioned data itself (ignores,
auto-props, etc.) than to general client behavior, where I've argued it
would be inappropriate.

To date, we have yet as a community to figure out a good way to implement a
more general server-side config feature. :-(

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2012-08-27 14:05:25 CEST

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