On Mon, Aug 10, 2015 at 3:40 AM, Stefan <luke1410_at_posteo.de> wrote:
> Hi,
>
> I'm wondering whether it would be reasonable to release another 1.7-build.
>
> 1.7.21 added support to build 1.7 using Visual Studio 2015. However there
> seemed to have been an oversight with neon, which misses the
> platformtoolset-setting in the project file (see: [PATCH] Fix SVN 1.7
> build issues with VS >2010).
>
> This leads to a linker issue, when u try to build SVN 1.7 out of the box
> using VS >= 2013.
>
> In the light of 1.7 no longer being supported it still might be a good
> idea to release a final 1.7 build so at least the stated VS 2015 is not
> broken forever for 1.7.
>
> If it's going to be released, then I'd also propose to apply the
> correctness-patch (see: [PATCH] correct ToolsVersion in VS project files)
> which also corrects the ToolsVersion-parameter for VS >= 2013.
>
I fine with canning 1.7.22 in favor of a "truly golden" 1.7.23.
After all, we rolled 1.7.22 for a similar reason not because
of actual user code breakage.
That said, it may require extra testing effort on Windows
(at least testing that vs2015 and vs2013 work) and I'd
rather have our Windows devs comment on that.
-- Stefan^2.
Received on 2015-08-11 16:37:29 CEST