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

Re: branching 1.14.x

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 14 Mar 2020 15:42:26 +0000

Stefan Sperling wrote on Sat, 14 Mar 2020 15:00 +0100:
> On Sat, Mar 14, 2020 at 09:25:21AM -0400, Mark Phippard wrote:
> > OK, then let's just move past it and hope it gets fixed in APR? If no one
> > raises their hand saying they are working on a fix, you should proceed as if
> > we are never going to fix this in our product. Otherwise, we are just stuck
> > here in limbo. Security bug or not, if no one is going to fix it then what is
> > there to wait for?
>
> At a minimum the test failures on Windows would need to be fixed.
>
> The easiest path forward we would be to revert the entire change,
> and then ship 1.14 with a known problem. I still hope that we'll
> manage to get enough support somehow to actually fix the problem,
> though I don't know how. I am not going to fix Window-specific bugs
> myself because I lack a dev environment and don't have any experience
> with developing on this platform.

Reminder: Active Apache committers can apply for MSDN licenses, which
AIUI include access to Windows VMs.

There are a few Windows build scripts lying around (e.g.,
tools/dev/windows-build/, tools/dev/build-svn-deps-win.pl, buildbots,
and that's just in our tree).

[Not trying to single out stsp here; just mentioning this for everyone.]

Cheers,

Daniel
Received on 2020-03-14 16:42:34 CET

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.