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

Re: wc format version bump for file externals?

From: <kmradke_at_rockwellcollins.com>
Date: Tue, 10 Jun 2008 08:52:23 -0500

> > > So I think we should bump the wc format, but Karl suggested we
discuss
> > > this.
> >
> > If we decide to do this, it'd be nice to decide earlier rather than
> > later. I know that Erik Hülsmann had some changes he wanted to make
for
> > 1.5, but held off because we weren't going to bump the format number.
> > We ended up doing so in the end, but IIRC, it was too late for him to
> > make the changes.
>
> If the tree conflicts branch gets merged before 1.6 (which I hope it
> will), then another wc format bump will be inevitable anyway.
>
> Besides, what's so bad with requiring people to check out new working
> copies when they upgrade to a new non-patch release? I hope we don't
> have users who consider checking out a new working copy the end of the
> world.

The biggest problem is users that use multiple clients. Think of a
windows user that has TortoiseSVN, Subclipse, and the command line
utils installed. They must be smart enough to upgrade all at the
same time. A lot of our users are more and more nontechnical,
so they might not even know all the steps.

(We also have the added burden of needing to support "old"
 Eclipse installs which may not even have a newer Subclipse
 build that matches the wc format.)

I'm not against bumping the format, just envisioning my pain
at trying to coordinate the upgrades for thousands of users
on a few hundred different projects. Ugh...

Looking forward to wc 2.0 which solves all the worlds problems... :)

Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-10 15:52:42 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.