I'm happy to announce Subversion 1.6.0-rc2 "Swordfish", available from:
http://subversion.tigris.org/downloads/subversion-1.6.0-rc2.tar.bz2
http://subversion.tigris.org/downloads/subversion-1.6.0-rc2.tar.gz
http://subversion.tigris.org/downloads/subversion-1.6.0-rc2.zip
http://subversion.tigris.org/downloads/subversion-deps-1.6.0-rc2.tar.bz2
http://subversion.tigris.org/downloads/subversion-deps-1.6.0-rc2.tar.gz
http://subversion.tigris.org/downloads/subversion-deps-1.6.0-
rc2.zip
The MD5 checksums are:
52c6d3c1ebf7c3ce3ee295274516d169 subversion-1.6.0-rc2.tar.bz2
25f723842ad16e3fed42a4a7b51b7966 subversion-1.6.0-rc2.tar.gz
fdac8bbd569fffa98e15afc9edb01340 subversion-1.6.0-rc2.zip
c81178c45e4c87e34a57057ef10b78a0 subversion-deps-1.6.0-rc2.tar.bz2
71d1e54686bf93915ca9d62233b5e554 subversion-deps-1.6.0-rc2.tar.gz
07e358f1b690ca64bb1dadd11adac45e subversion-deps-1.6.0-rc2.zip
The SHA1 checksums are:
a9a4a2ac344a38bd1fd9343eba909dbb07f8959d subversion-1.6.0-
rc2.tar.bz2
75356edfcf5bfb753414ca80a2249188483712ba subversion-1.6.0-
rc2.tar.gz
166bd6c9821a4182cc7e4725e1fab1d169367cf1 subversion-1.6.0-rc2.zip
458d579217964d2a2ef052f5d02aee1c9baeefb0 subversion-deps-1.6.0-
rc2.tar.bz2
08885ef3519f741177bc350dd56a4b3ac5359433 subversion-deps-1.6.0-
rc2.tar.gz
1adf9aa634721936659b3a3049df9f21890292e9 subversion-deps-1.6.0-
rc2.zip
PGP Signatures are available at:
http://subversion.tigris.org/downloads/subversion-1.6.0-rc2.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-1.6.0-rc2.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-1.6.0-rc2.zip.asc
http://subversion.tigris.org/downloads/subversion-deps-1.6.0-rc2.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-deps-1.6.0-rc2.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-deps-1.6.0-rc2.zip.asc
For this release, the following people have provided PGP signatures:
Senthil Kumaran S [1024D/6CCD4038] with fingerprint:
8035 16A5 1D6E 50E2 1ECD DE56 F68D 46FB 6CCD 4038
Paul T. Burba [1024D/53FCDC55] with fingerprint:
E630 CF54 792C F913 B13C 32C5 D916 8930 53FC DC55
Karl Fogel [1024D/DB00A248] with fingerprint:
B77E 8FB2 112F 9637 2E3E 3F08 BC9D BB13 DB00 A248
Bert Huijben [1024D/9821F7B2] with fingerprint:
2017 F51A 2572 0E78 8827 5329 FCFD 6305 9821 F7B2
Hyrum K. Wright [1024D/4E24517C] with fingerprint:
3324 80DA 0F8C A37D AEE6 D084 0B03 AE6E 4E24 517C
Branko Čibej [2048R/C8628501] with fingerprint:
8769 28CD 4954 EA74 87B6 B96C 29B8 92D0 C862 8501
Stefan Sperling [1024D/F59D25F0] with fingerprint:
B1CF 1060 A1E9 34D1 9E86 D6D6 E5D3 0273 F59D 25F0
Mark Phippard [1024D/035A96A9] with fingerprint:
D315 89DB E1C1 E9BA D218 39FD 265D F8A0 035A 96A9
This is a public Release Candidate for Subversion 1.6.0. This release
starts the soak period for 1.6.0 and pending a lack of showstopper
bugs, it is anticipated that this will become the final release in 4
weeks.
The term 'release candidate' means the Subversion developers feel that
this release is stable and ready to be tested in production use. If
this testing confirms its readiness, this candidate version will
become the final released version. Therefore, 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.6.0-
rc2 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.6.x release series are not yet complete, but
may be found at:
http://subversion.tigris.org/svn_1.6_releasenotes.html
You can find the list of changes between 1.6.0-rc2 and earlier
versions at:
http://svn.collab.net/repos/svn/tags/1.6.0-rc2/CHANGES
Questions, comments, and bug reports to users_at_subversion.tigris.org.
Thanks,
- The Subversion Team
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1200070
Received on 2009-02-20 20:10:20 CET