After much trail and error, I'm happy to announce Subversion 1.5.0-rc4,
available from:
http://subversion.tigris.org/downloads/subversion-1.5.0-rc4.tar.bz2
http://subversion.tigris.org/downloads/subversion-1.5.0-rc4.tar.gz
http://subversion.tigris.org/downloads/subversion-1.5.0-rc4.zip
http://subversion.tigris.org/downloads/subversion-deps-1.5.0-rc4.tar.bz2
http://subversion.tigris.org/downloads/subversion-deps-1.5.0-rc4.tar.gz
http://subversion.tigris.org/downloads/subversion-deps-1.5.0-rc4.zip
The MD5 checksums are:
477503b5ce6b99370814144417b8c994 subversion-1.5.0-rc4.tar.bz2
905fc5030be179d4d387803b8397668a subversion-1.5.0-rc4.tar.gz
8efe4cb335760e62a37c5dc6a2931086 subversion-1.5.0-rc4.zip
df101d0e6e014a31d3b3f400f7e10c09 subversion-deps-1.5.0-rc4.tar.bz2
a6728d38d1878c1b230d9c27fbae1881 subversion-deps-1.5.0-rc4.tar.gz
b2a46082779df27feb99125c252f304a subversion-deps-1.5.0-rc4.zip
The SHA1 checksums are:
b4a10cf4adda2b92f3e0e23a9dbf386206c7d9a4 subversion-1.5.0-rc4.tar.bz2
f26831c8b7ae0a172716be87f8a110445814a5fb subversion-1.5.0-rc4.tar.gz
ded581a1eb3fba9a30807fbbe58e221e68c2e672 subversion-1.5.0-rc4.zip
c87daf151fe0a5c5d48e40fba09c24b50de2c21f subversion-deps-1.5.0-rc4.tar.bz2
4a7ac5073f1bb56ead4b030e0cccfba0ec8cb3ea subversion-deps-1.5.0-rc4.tar.gz
0ac75ba0680e00693f1b34b0eeecd2ce045e827c subversion-deps-1.5.0-rc4.zip
PGP Signatures are available at:
http://subversion.tigris.org/downloads/subversion-1.5.0-rc4.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-1.5.0-rc4.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-1.5.0-rc4.zip.asc
http://subversion.tigris.org/downloads/subversion-deps-1.5.0-rc4.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-deps-1.5.0-rc4.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-deps-1.5.0-rc4.zip.asc
For this release, the following people have provided PGP signatures:
Blair Zajac [1024D/DA561D91] with fingerprint:
3FAE C7E1 ADE8 572F 613C F086 C572 2326 DA56 1D91
Karl Fogel [1024D/DB00A248] with fingerprint:
B77E 8FB2 112F 9637 2E3E 3F08 BC9D BB13 DB00 A248
Ivan Zhakov [1024D/C4F3A281] with fingerprint:
9D3C 5860 6A64 74BF 591D F3A1 F60D 1980 C4F3 A281
Hyrum K. Wright [1024D/4E24517C] with fingerprint:
3324 80DA 0F8C A37D AEE6 D084 0B03 AE6E 4E24 517C
Kamesh Jayachandran [1024D/ED184C2C] with fingerprint:
3E5B 5C1D 1CA6 A611 2787 9B4B DD61 EFC8 ED18 4C2C
C. Michael Pilato [1024D/1706FD6E] with fingerprint:
20BF 14DC F02F 2730 7EA4 C7BB A241 06A9 1706 FD6E
Julian Foad [1024D/353E25BC] with fingerprint:
6604 5A4B 43BC F994 7777 5728 351F 33E4 353E 25BC
Paul T. Burba [1024D/53FCDC55] with fingerprint:
E630 CF54 792C F913 B13C 32C5 D916 8930 53FC DC55
Mark Phippard [1024D/035A96A9] with fingerprint:
D315 89DB E1C1 E9BA D218 39FD 265D F8A0 035A 96A9
This is the first public Release Candidate for Subversion 1.5.0, as
serious problems were found with the previous three release candidates
before they were made publicly available.
The term 'release candidate' means the Subversion developers feel that
this release is stable and ready for production use, so we encourage
people to test this release thoroughly.
As a note to operating system distro packagers: while we wish to have
this release candidate widely tested, we do not feel that it is ready
for packaging and providing to end-users through a distro package
system. Packaging a release candidate poses many problems, the
biggest being that our policy lets us break compatibility between the
release candidate and the final release, if we find something serious
enough. Having many users depending on a release candidate through
their distro would cause no end of pain and frustration that we do not
want to have to deal with. However, if your distro has a branch that
is clearly labeled as containing experimental and often broken
software, and explicitly destined to consenting developers and
integrators only, then we're okay with packaging the release candidate
there. Just don't let it near the end users please.
Please note that due to various improvements made to the working copy
library, the working copy format has changed. Using Subversion 1.5.0-alpha2
on any working copy created by previous versions of Subversion will
TRANSPARENTLY upgrade your working copy, which means that production-ready
versions of Subversion will no longer be able to read it! Please be careful,
if you have two versions of Subversion running on your machine, to not use
the wrong version on a production working copy. If you inadvertently do
upgrade your working copy, you can use the new
tools/client-side/change-svn-wc-format.py script to restore working copy
compatibility with previous versions of Subversion.
Release notes for the 1.5.x release series may be found at:
http://subversion.tigris.org/svn_1.5_releasenotes.html
You can find list of changes between 1.5.0-rc4 and earlier versions at:
http://svn.collab.net/repos/svn/tags/1.5.0-rc4/CHANGES
Questions, comments, and bug reports to users_at_subversion.tigris.org.
Thanks,
- The Subversion Team
Received on 2008-04-24 18:03:11 CEST