I'm happy to announce the release of Apache Subversion 1.9.0-alpha2.
Please choose the mirror closest to you by visiting:
The SHA1 checksums are:
PGP Signatures are available at:
For this release, the following people have provided PGP signatures:
Ben Reser [4096R/16A0DE01] with fingerprint:
19BB CAEF 7B19 B280 A0E2 175E 62D4 8FAD 16A0 DE01
Bert Huijben [4096R/CCC8E1DF] with fingerprint:
3D1D C66D 6D2E 0B90 3952 8138 C4A6 C625 CCC8 E1DF
Branko Čibej [4096R/A347943F] with fingerprint:
BA3C 15B1 337C F0FB 222B D41A 1BCA 6586 A347 943F
Johan Corveleyn [4096R/010C8AAD] with fingerprint:
8AA2 C10E EAAD 44F9 6972 7AEA B59C E6D6 010C 8AAD
Philip Martin [2048R/ED1A599C] with fingerprint:
A844 790F B574 3606 EE95 9207 76D7 88E1 ED1A 599C
Stefan Fuhrmann [4096R/57921ACC] with fingerprint:
056F 8016 D9B8 7B1B DE41 7467 99EC 741B 5792 1ACC
This is a pre-release for what will eventually become Apache Subversion
1.9.0. It does contain some known issues (this list is not exhaustive):
* Several issues with FSX (it is still experimental after all).
* svnserve SASL support is broken.
A pre-release means the Subversion developers feel that this release
is ready for widespread testing by the community. There are known issues
(and unknown ones!), so please use it at your own risk, though we do
encourage people to test this release thoroughly. Of particular note, please
remember than persistent data, such as the working copy or repository
formats may change before the final release, and there may not be an
upgrade path from the pre-releases to the final. In this particular case, since
many of the changes have been to the repository formats and this is
only an alpha it is highly likely that incompatible format changes will be made
before the final 1.9.0 release.
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.
With all the warnings given, we would especially like feedback on the following:
* New 'svn auth' subcommand.
* New reverse 'svn blame' functionality (-r M:N with M>N).
* Improvements to the interactive conflict resolution menus.
* FSFS format 7.
If you have any thoughts about the changes made in 1.9.0-alpha2 we would really
appreciate your feedback (even if they are not about the above things).
feedback this early in the development process provides us an opportunity to make
significant changes we otherwise would not make with a release candidate. Feedback
on 1.9.0-alpha2 should be directed to the users_at_subversion.apache.org mailing list.
Release notes for the 1.9.x release series may be found at:
You can find the list of changes between 1.9.0-alpha2 and earlier versions at:
Questions, comments, and bug reports to users_at_subversion.apache.org.
- The Subversion Team
Received on 2014-04-14 17:56:50 CEST