On 10/6/05, firstname.lastname@example.org <email@example.com> wrote:
> Let's set a date for the first 1.3.0 release candidate tarball. How
> about Wednesday, October 12th? Ben Reser, does that work for you?
We need to fix the crashes on Windows before the Python bindings will
be ready for a release candidate. Do you think the release could wait
> Details, and possible items for discussion:
> The 1.3.x/STATUS file looks pretty good. Most of what's in there is
> bugfixes, and I think we'll be able to ensure that the important ones
> get enough review & votes by Wedesday to go in. No problems there.
> On http://subversion.tigris.org/svn_1.3_releasenotes.html there are
> still a few pending items. Some of them might be done now, others I'm
> pretty sure are not. Here are the relevant items:
> - Is the Python bindings Trac test crash on Windows, solved? I
> think not; at least, the last message in the thread is
> http://svn.haxx.se/dev/archive-2005-09/1047.shtml, and it's a
> disgruntled statement from Brane: "Ah. Well. Yes, the trac tests
> crash again.. :("
No, this isn't solved. To fix the crash issues in the Windows
bindings, we need to compile Subversion on Windows with debug symbols,
and use a debugger to find out where the bindings are crashing during
the test suite. C. Mike, would you be able to take a look at this?
> - We haven't upgraded server-side Python scripts to use the new
> automatic memory management API. On the one hand, this doesn't
> need to block 1.3 -- it's a nice-to-have, not a must-have. On the
> other hand, David James *already* wrote the patch to do it:
> I think we should apply it to trunk, and port the change to 1.3.x,
> if for no other reason than that this is exactly what release
> candidates are for. It's the best way to get the new bindings the
> testing they need. Thoughts?
I'd like to commit the patch, but I don't know enough about the
affected scripts to test them properly. Anyone able to help?
> Aside from the above, is there anything else we need on the 1.3.x
If the Windows crashes are fixed, then our release candidate is ready to go.
P.S. The install-swig-py target can fail in a VPATH setup, if you are
building from a release build, and make the "install-swig-py" target
before making the "swig-py" target. Max Bowsher is currently working
on a fix. I'm hoping this fix will be included, but it is a minor
David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Oct 7 05:30:41 2005