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

svn 1.1 RC2 status

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-23 18:49:12 CEST

In my perfect world, I'd love to get a subversion-1.1.0-rc2 tarball
released early next week, maybe Monday or Tuesday. That's my goal, at
least. :-)

We've already merged several small bugfixes to the 1.1.x branch since we
released rc1:

* fixed: segfault when history-following hits 'empty' revision (r10368)
* fixed: bug in symlink timestamp setting (r10351)
* fixed: prevent canonicalized URIs from ending in '/' (r10317)
* if no BDB configured, default to fsfs back-end. (r10299, 10338)
* tweak description of --without-berkeley-db (r10313)
* tweak description within repos/README.txt (r10296)
* tweaks to HACKING (r10264) and swedish .po translation (r10243)

In addition, there are currently three things to backport in the 1.1.x
STATUS file, as well as two other things on the plate for backport:

* ? dist.sh -- new ability to creates win32 zipfiles
* ? make svnserve default-realm = uuid (ghudson, if easy to do)
* backport: svnserve md5 space-in-name bug
* backport: python bindings busted on OSX
* backport: windows 'blame' bug from lundblad

And then there are the really serious bugs. I think there are two
issues completely blocking an rc2 release:

* libtool 1.4.3 in rc1 tarball seems to not work on OSX 10.3 ??
* issue 1968: mysterious 'invalid arg' bdb errors everywhere

Ben Reser has access to an OSX machine, and is investigating the first
bug. I'm hoping that the rest of us (i.e the whole developer community)
can "crack down" on issue 1968 and figure out what the heck is going
on. The sheer number of issue 1968 reports is starting to scare me.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 23 18:51:25 2004

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.