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

Subversion 1.1.0 Release Candidate 2 released.

From: Ben Reser <ben_at_reser.org>
Date: 2004-08-10 23:59:32 CEST

The second release candidate of Subversion 1.1.0 is ready and
available from:

   http://subversion.tigris.org/tarballs/subversion-1.1.0-rc2.tar.gz
   http://subversion.tigris.org/tarballs/subversion-1.1.0-rc2.tar.bz2
   http://subversion.tigris.org/tarballs/subversion-1.1.0-rc2.zip

The MD5 checksums are:

   53d53cbbac165106a1edf75f54cb5ea8 subversion-1.1.0-rc2.tar.gz
   ecd53e9f065739023da768891b83b70e subversion-1.1.0-rc2.tar.bz2
   223e92ea881f9183fd4d7edf4de1c7af subversion-1.1.0-rc2.zip

PGP Signatures are available at:
   http://subversion.tigris.org/tarballs/subversion-1.1.0-rc2.tar.gz.asc
   http://subversion.tigris.org/tarballs/subversion-1.1.0-rc2.tar.bz2.asc
   http://subversion.tigris.org/tarballs/subversion-1.1.0-rc2.zip.asc

PGP Signatures will be made by the following person(s) for this release:
   Ben Reser [1024D/641E358B] with fingerprint:
   42F5 91FD E577 F545 FB40 8F6B 7241 856B 641E 358B

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. The final 1.1.0 release is
scheduled for mid-September, in order to provide plenty of time for
testing.

The changes between 1.1.0-rc1 and 1.1.0-rc2 are listed below.
New 1.1 features are explained in detail in our release notes,
located at:
  
    http://subversion.tigris.org/svn_1.1_releasenotes.html

You can find the list of the changes between 1.0.6 and the 1.1.0-rc2 at:

    http://svn.collab.net/repos/svn/branches/1.1.x/CHANGES

Questions, comments, and bug reports to users_at_subversion.tigris.org.

Thanks,
-The Subversion Team

--------------------8-<-------cut-here---------8-<-----------------------

User-visible-changes:
* cmdline client now supports psuedo-IRIs and autoescapes chars (issue #1910)
* print verbose BDB error messages (r10557, r10566)
* fixed: make svnserve's authn work on usernames with spaces (r10385)
* fixed: have svnserve use repos UUID as default authn realm (r10394)
* fixed: win32 prompting bug (r10431)
* fixed: segfault when history-following hits 'empty' revision (r10368)
* fixed: bug in symlink timestamp setting (r10351)
* fixed: 'svn cp dir1 dir2' containing a versioned symlink (issue 1986)
* fixed: overzealous out-of-dateness checks in 'svn cp wc URL' (issue 1994)
* fixed: don't URI-encode path in mod_dav_svn XML listings (r10461)
* tweak description of --without-berkeley-db (r10313)
* tweak description within repos/README.txt (r10296)
* tweaks to HACKING, INSTALL, and mailer.py (r10464)
* many .po translation updates

Developer-visible-changes:
* fixed: OS X build problem (r10473)
* fixed: potential mod_dav_svn crashes/memleaks (r10478)
* fixed: better 'svnadmin verify' verification (r10508, r10509)
* fixed: FSFS: do checksumming when reading (r10507)
* fixed: FSFS: handling of non-canonical copyfrom data (r10480)
* fixed: encoding of get_repos_url_result (r10353, 10375)
* fixed: prevent canonicalized URIs from ending in '/' (r10317)
* fixed: don't assume DEFAULT_OS_TYPE is bdb (r10405)
* if no BDB configured, default to fsfs back-end. (r10299, 10338)
* remove 'svn_node_special' from svn_node_kind_t (r10505)
* perl bindings: many code/build fixes (r10400, 10401, 10440, 10458)
* python bindings: fix build and swig bugs (r10422, 10410, 10450, 10561)
* javahl bindings: new 'svn info'/'svn log -v' (r10462, 10491, 10493, 10517)
* win32 build: new --enable-bdb-in-apr-util option (r10398, 10389)
* dist.sh: new ability to create win32 .zip distros

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 11 00:00:29 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.