Ben Collins-Sussman wrote:
> I just committed a first draft of the 1.3.0 CHANGES entry, so at
> least our rc1 tarball is no longer blocking on that.
> * Despite all the work on the wc-replacements branch, and the fact
> that it got merged to trunk recently, I see no nomination to
> backport it to 1.3.x. So I guess this will be a 1.3.1 bugfix as
It is a large changeset, but if people want to nominate it, it should
be possible to have it approved by three people who've already
reviewed the branch.
> * Issue 960 was resolved in trunk months ago -- the working copy now
> stores the repos_root URL as a separate field in .svn/entries. But
> it seems like nothing is using this yet. Is the Master Plan to get
> this out to everyone in 1.3, then build features on top of it later
There is really litterally nothing being done with it? Not even
display in 'svn info' ? The comments on #960 suggest that alone might
be useful to some third party scripts.
Now, for a review of the still-open issues before we can roll the
* Problems between a 1.3.x client and a 1.2.1 server. This was
pinned down as being a known bug in Neon 0.25.0, which subsequent
releases fix. The discussion on what to do about it is getting a
little sidetracked (starts at
http://svn.haxx.se/dev/archive-2005-10/0626.shtml), but it seems
the logical way out is to drop support for 0.25.0. In the few
cases where people want to bypass this, we already have a
configure flag to do so.
* Ruby bindings segfault. David James has identified this to be a
pool management bug similar to ones already seen in the python
bindings (see issue #2172), and is working on a fix. The core
code changes needed for the fix have been nominated, and need
* Build issues with the Perl bindings.
It seems this was resolved in a way by reverting r16486, going
back to the lesser of two bugs. Is this the final word on the
issue, or are there plans to also correct the lesser bug?
* Crash in python bindings on windows
reports a possible threading problem in the python bindings.
There is little information about versions this bug occurs in, but
this should be put to bed one way or another.
* The fix for issue #1911 is nominated and needs one more approval.
I'll be taking a look at it a little later.
* svn_1.3_releasenotes.html needs to be rewritten to be more in the
style of the previous release notes, rather than an RC TODO. Ben
Collins-Sussman is working on this.
Finally, a personal message for Ben Reser: Ben, can you make sure you
have SWIG 1.3.25 installed for cutting the release tarballs? You're
now the only one who needs SWIG installed, as the releases now have
If I've missed anything, please say so. I think if this list doesn't
grow any more, we should be able to cut the RC later today or tomorrow.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Oct 14 22:28:10 2005