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

RE: rc1 is DOA. What now?

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 24 Aug 2011 15:18:49 +0200

> -----Original Message-----
> From: Branko Čibej [mailto:brane_at_xbc.nu] On Behalf Of Branko Cibej
> Sent: woensdag 24 augustus 2011 15:07
> To: Bert Huijben
> Subject: Re: rc1 is DOA. What now?
> On 24.08.2011 10:38, Bert Huijben wrote:
> > How would you answer an e-mail from your sysadmin that tonight before
> you go
> > home you have to remove all locks from all your working copies because
> > otherwise tomorrow your working copies are broken?
> I would mail his manager with a suggestion to fire that sysadmin,
> because he wasn't doing his job right.
> > I call this a show stopper; and as I suggested before suggesting these users
> > to wait until 1.7.1 is the same as calling this a show stopper.
> > And it also breaks the perfect stability track record we had with a
> > known-in-advance broken release.
> >
> > In my opinion this issue must be fixed by 1.7.0.
> You're overreacting. Compare this limitation to all the other
> limitations of the 1.7 WC upgrade (by the way, where's the list of those
> anyway?).

The complete list:
* You can't have loggy items queued in your working copy

All other working copy states are fully supported for upgrade for the step from 1.0-1.6 -> 1.7+

There are unsupported scenarios for the intermediate development formats, but there are no other limitations for the supported formats.

Received on 2011-08-24 15:19:21 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.