[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: Julian Foad <julian.foad_at_wandisco.com>
Date: Wed, 24 Aug 2011 13:17:04 +0100

Hyrum K Wright wrote:
> On Wed, Aug 24, 2011 at 6:07 AM, Julian Foad <julian.foad_at_wandisco.com> wrote:
> > Having read the discussion elsethread, I now consider this a blocker and
> > that also seems to be the consensus. So we can't release 1.7.0 with
> > this bug; it has to be fixed. That in turn means the supposed 'RC1' is
> > no longer an RC at all. [...]
> So the grander feeling seems to be: scuttle rc1 (which already has the
> votes for release)

I interpreted Bert's "+1 as it passes regression tests but -1 to release
as Subversion 1.7.0" the same as a "-1" vote for RC1, based on my
understanding of the requirements for an RC.

To make it plain, I hereby change my own RC1 vote to -1.

> and reroll an rc2. The fix for the 'upgrade with
> lock' issue is already on 1.7.x, so we can do this pretty much
> whenever we'd like. I'm inclined to do it tomorrow, following the
> normal pattern.

+1 to that.

- Julian
Received on 2011-08-24 14:17:44 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.