> -----Original Message-----
> From: Bert Huijben [mailto:[email protected]]
> Sent: dinsdag 23 augustus 2011 11:08
> To: 'Hyrum K Wright'; 'Subversion Development'
> Subject: RE: 1.7.0-rc1 up for testing / signing
>
>
>
> > -----Original Message-----
> > From: Hyrum K Wright [mailto:[email protected]]
> > Sent: vrijdag 19 augustus 2011 20:24
> > To: Subversion Development
> > Subject: 1.7.0-rc1 up for testing / signing
> >
> > Here it is: the first Release Candidate for Subversion 1.7.0. You can
> > fetch the proposed tarballs from here:
> > http://people.apache.org/~hwright/svn/1.7.0-rc1/
> >
> > The magic rev is r1159696; please post signatures at the normal location:
> > http://work.hyrumwright.org/pub/svn/collect_sigs.py
> >
> > This is a release candidate, meaning if all goes well it (or something
> > very much like it) will become the final release. Please test this as
> > if it were the final release, understanding that there will be bugs in
> > any software we ship. <insert lecture about perfect being enemy of
> > the good here>
>
> +1 to release as 1.7.0-RC1 as all tests pass for me.
> -0 to release as Subversion 1.7.0
Ok, make that a -1 to release as Subversion 1.7.0
Subversion working copies that contain 'svn lock'-style locks can't be upgraded
by our current upgrade code.
(We are mixing two sqlite handles in the upgrade code and the code that inserts
a lock checks if a node exists using a db handle that can't look inside the
transaction of the other handle)
I'm working on a fix and a regression test. (Should be fixed in a few hours)
Thanks to Markus Schaber for providing this testcase.
Bert
