Re: Setting a date for 1.3 RC tarball.

kfogel@collab.net writes:

> > 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?
>
> Or if not CMike, is there someone else with a Windows box and a little
> bindings experience around?
>
> (I've pinged CMike privately in case he didn't see this thread,
> though.)

CMike currently has no Windows build environment. That setup is on a
computer in some foam packing in a box in a ministorage unit in
TheMiddleOfNowhere, North Carolina.

>
> > > - 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:

[...]

> An open question: can we release the upgraded versions in 1.3.1 or
> later? Or should it wait until 1.4. I guess 1.4, much as I hate to
> say it.

Nah, 1.3.1 would be fine. The behavior of the scripts isn't changing,
the scripts don't themselves expose APIs, etc. This tweak would be
along the lines of a memory usage bugfix, and is a perfectly valid
candidate for a patch release.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org