> I have repeatedly heard similar complaints and would therefore > prefer > an explicit 'svn upgrade' upon 1.x to 1.y upgrades for working > copies > starting with 1.7. And I have never heard anyone asking for the > auto-upgrade > feature to be kept. > > The CLI client can print an error. GUI clients can show a window > prompting > the user whether to run an upgrade or bail out. > > This does not harm people using a single client much, but helps > users > who use several clients simultaneously a lot (they don't have to > get > fresh WCs to continue getting work done). > > We could also add a configuration option to ~/.subversion/config > that > causes working copies to always be auto-upgraded, defaulting to > 'off'. >
I know this isn't a democracy, but if you are looking for votes this does seem like a more reasonable way to handle it. Especially in keeping with the goal of "not changing your data unless you tell it to" meme. BOb
