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

RE: 1.7.0-rc1 up for testing / signing

From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 23 Aug 2011 11:07:47 +0200

> -----Original Message-----
> From: Hyrum K Wright [mailto:hyrum.wright_at_wandisco.com]
> 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

I don't think we tried hard enough to clear STATUS to make this a valid 1.7.0 for me.
There are still a few items that should have been resolved.
The only reason to make this a 1.7.0 would be that we assume that all users just wait until 1.7.1 anyway, and I don't want to encourage users to do that.

Visual Studio 2010 SP1 x86
Windows 7 Business X64

[fsfs | bdb] x [ra_local | ra_svn | ra_neon | ra_serf] + JavaHL + SharpSvn

Apr 1.4.5+r960671
Apr-Util 1.3.12
Apr-Iconv 1.2.11
BDB 4.4.20
Cyrus Sasl 2.1.23
GetText 0.17
Httpd 2.2.19
Junit 4.8.1
Neon 0.29.6
OpenSSL 1.0.0d
Serf 1.0.0
SQLite 3.7.7.1
ZLib 1.2.5

In the last few days I had a few bug reports for SharpSvn from users testing against 1.7. Those have been resolved without requiring additional patches to Subversion.

        Bert
Received on 2011-08-23 11:08:27 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.