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

Time for a 1.3.1 release? (without the bdb fixes)

From: David James <djames_at_collab.net>
Date: 2006-01-28 00:46:09 CET

Now that Subversion 1.3.0 has been out for a while, we have
accumulated a number of very useful fixes for 1.3.1. I'd say it's time
for a 1.3.1 release, as soon as we can finish voting on the items in
STATUS. Could we make it a goal to wrap up the voting next week, so
that we can release 1.3.1 in short order?

Given this schedule, I'd like to propose that we delay the BDB fixes
(proposed by brane) until after 1.3.1. These fixes to BDB library will
be very helpful for end users, but I think we need to test them
thoroughly on production repositories (such as svn.collab.net) for a
few months before we push it out in any release.

That issue aside, I've looked through STATUS and our log messages for
the 1.3.x branch to make a summary of what has been proposed or
approved for 1.3.1. Here's an abbreviated summary of the user-visible

Core libraries:
 - Fix crashes on mixed-case https:// URLs (r18042)
 - Fix mv --force segfaults on unversioned files (r17242, r17243)
 - Fix verbose list when used with peg revisions over ra_dav (r17485, r18027)
 - Make mod_dav_svn log all the errors in a given chain, rather than
just the first one
SWIG bindings:
 - Update for compatibility with SWIG 1.3.26 / 1.3.27 (r17280, r18172, r18205)
Ruby/SWIG bindings:
 - Fix memory leaks (r17795, r17811)
 - Fix character-set conversion bugs (r17726, r17925)
 - Fix garbage collection segfaults (r17627)
Python/SWIG bindings:
 - Fix memory leaks (r18230)
 - Fix assertion errors (r17792)
 - Fix linking errors on Solaris 10 (r17910)

David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 28 00:46:32 2006

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

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