I'm going to get on a plane soon and be (more or less) offline for
most of next week. Is there someone who can take on the "keeping
track of the big picture" role for 1.3.0?
Right now, this basically means knowing what is delaying 1.3.0 RC 1,
and then prodding/coding/reviewing as necessary to get the obstruction
to go away. For problems that might last longer than a few hours,
it's good to make "TODO" notes in www/svn_1.3_releasenotes.html, to
help everyone keep the global picture in focus.
Here are all the problems I'm currently aware of:
* Problems between a 1.3.x client and a 1.2.1 server, pointed out by
John Peacock, who narrowed it down to having something to do with
Neon 0.25.0 (since 0.24.7 doesn't seem to have the problem). See
and its followups for details.
* The Ruby bindings seg fault in their test suite if you build with
"--enable-pool-debug=yes". John Szakmeister, in this message
starts it off, then David James asks Kouhei to take a look here:
[Meta comment: Should it worry us that there's basically only
person who knows how to keep the SWIG-Ruby bindings in shape? We
have a minimum two-person-per-language policy when it comes to
translations; shouldn't we at least have the same for the
bindings? Kouhei, this is not a complaint about you, of course;
you're doing great stuff, it's just a question of what would
happen if you took a vacation. :-) ]
* According to David James in this message:
"John Peacock pointed out some build issues with the Perl
bindings, where installed libraries link to build-dir libraries.
Max, will reverting r16486 fix the problem? If so, perhaps we
should revert r16486 and propose the revert for backport to the
1.3.x branch. See: http://svn.haxx.se/dev/archive-2005-10/0556.shtml"
I don't think there's been any answer to David's question yet.
* r16693, a simple crash fix in libsvn_ra_dav. It's already got two
votes in 1.3.x/STATUS, just needs one more person to review and
There are no TODO notes in svn_1.3_releasenotes.html for any of these
yet, but there could be.
Anyway, I wish I could see this through to the RC tarball, but it
looks like there won't be time. Someone please be shepherd...
www.collab.net <> CollabNet | Distributed Development On Demand
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Oct 13 23:16:00 2005