Re: Automatic upgrading of WC versions and the pain it causes

[Max Bowsher]
> I would like to create a new configuration file setting,
> config.[miscellany].allow-wc-upgrade, which defaults to yes,
> preserving the status quo, but which someone who knows that they will
> be working with multiple client versions can set to false, which will
> cause new clients to exit with an error when accessing an old WC,
> rather than silently upgrading it.

Well, if it is convenient, I'd suggest making it exit only if it would
have to *write* to the repository metadata. Obviously you need to
maintain the ability to read old metadata (to perform the upgrade), so
it doesn't seem like it would be much of a burden to continue to
support read-only access.

Also, if someone sets allow-wc-upgrade to no, I hope you're also
planning to support a way to tell the client to upgrade the repository,
be that a '--force'-like flag or a subcommand.