On Tue, May 14, 2013 at 3:18 PM, Ben Reser <ben_at_reser.org> wrote:
> Here it is: the second Release Candidate for Subversion 1.8.0. You can
> fetch the proposed tarballs from here:
> The magic rev is r1482456
> 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
Other than the expected differences in
is identical to
 See http://svn.haxx.se/dev/archive-2013-05/0079.shtml) for details.
SHA1 checksum of
>gpg2 --verify subversion-1.8.0-rc2.zip.asc
gpg: Signature made 05/14/13 15:11:59 Eastern Daylight Time using RSA
key ID 16A0DE01
gpg: Good signature from "Ben Reser <ben_at_reser.org>"
gpg: aka "Ben Reser <breser_at_apache.org>"
gpg: aka "Ben Reser <ben.reser_at_wandisco.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 19BB CAEF 7B19 B280 A0E2 175E 62D4 8FAD 16A0 DE01
[Release-Build] x[ fsfs | bdb ] x [ ra_file | ra_svn | ra_serf) ]
Ruby bindings (Ruby test suite patched with the r1480344 group so I
can run the tests -- see
includes *no* changes to the bindings themselves, only the test
All Tests Pass
MS Windows 7 Home Premium Service Pack 1
Microsoft Visual Studio 2008 Version 9.0.30729.1 SP
Python: 2.7.2 (ActivePython 188.8.131.52)
Ruby: ruby 1.8.7
user: "Paul T. Burba <pburba_at_collab.net>"
4096-bit RSA key, ID 56F3D7BC, created 2012-12-11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
-----END PGP SIGNATURE-----
> To all distributors and binary packagers: This isn't the final
> release. It *won't* be the final release for a few weeks yet, so
> please don't ship it as such. In any case, don't distribute any
> releases based upon these tarballs until we complete our signature
> gathering process and officially announce the release.
> Reminder that the STATUS file is still for 1.8.0, please be careful
> about moving changes to the approved section and only move changes
> that appropriate to be merged at this point (i.e. changes that would not
> restart our soak). If we have changes we want to put into 1.8.1, it's fine
> to put them in the STATUS file and vote on them, just please do not move
> them to the approved section. It may be helpful to refer to this section of
> our documentation when determining what can done to the 1.8.x branch
> during our soak period:
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Received on 2013-05-15 03:34:27 CEST