On Fri, Aug 27, 2010 at 05:54:38PM +0100, Julian Foad wrote:
> The trouble is, people often won't find out until some time after
> they've upgraded, especially if it's a WC they aren't working on at the
> moment and they try to come back to work on it some weeks later. And
> for most people un-upgrading in order to do fix it isn't a practical
That's reality, but not exactly best-practice.
If your local mods have been lying in the working copy for weeks,
they're probably not that important. If it's important, it should
be checked in, or backed up in patch, or something.
But yes, I can see how communicating this problem in a large
organisation can be hard. The admin installs the new software,
working copies stop working, and weeks later they still get support
calls about subversion being broken.
Still, we should dicide on a reasonable feature set for 1.6->1.7 working
copy upgrades, and try not to get carried away by the huge amount of
complicated details of this problem.
Received on 2010-08-27 19:15:26 CEST