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

Re: Subversion 1.2.0 RC3 (final candidate) on Monday?

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-05-07 02:40:44 CEST

kfogel@collab.net wrote on 05/06/2005 02:57:57 PM:

> What would we say to rolling rc3 on Monday? Ben Reser, does that work
> for you? That would give us the weekend to vote on pending STATUS
> items (of which there are currently 10, but only 2 or 3 have any
> complexity to them).
> Assuming no showstoppers, rc3 would be the final candidate,
> essentially identical to 1.2.0, which would be released one week
> later. Of course, were we to find a bug in rc3 severe enough to
> warrant rc4, that would re-start the 1-week resoak.

I guess it is not a show stopper, but recall that I have a pending issue
that merge over http:// from the JavaHL binding crashes the JVM on
Windows. Patrick Mayweg is planning to look at it when he gets home from
vacation this weekend. He did some preliminary checking and this looks
like it might be a tough problem to solve. The issue is that Java uses a
really small stack size on Windows and there is no reasonable way to alter
it or control it. Some changes in the merge API have apparently caused
the stack usage to exceed this limit. Unless there is some way to compile
the JavaHL DLL so that it allocates all memory from the heap, I do not
know how this could be fixed.

Hopefully Patrick will find some clever solution.

Just wanted you to be aware of it. I am really not sure what we are doing
to do about this in Subclipse. It is pretty nasty to just crash the
user's IDE.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 7 02:41:36 2005

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.