Rainer Jung in gmane.comp.apache.devel (Thu, 15 Mar 2018 18:15:13 +0100): >The artefacts are on the mirrors and out in the wild, so we can not get >them back. Best is to soon proceed with the release and document the >mod_proxy_balancer on Windows regression in the announcement.
+1 >About "not catching ahead of time": it would be great, if at least one >of us had a Windows system with the ability to run the test suite. Something that crosses my mind from time to time: appveyor.com is free for open source projects. PHP uses it for running the test suite: https://ci.appveyor.com/project/php/php-src/build/master.build.6478/job/ios1a5p0vjuqkmik#L5609 Libexpat does the same: https://ci.appveyor.com/project/libexpat/libexpat/build/libexpat-131 In these test they are building Debug\expatd.dll and running the tests in Debug mode, but with some adjustments a static release\expat.lib can also be built: https://ci.appveyor.com/project/Jan-E/libexpat/build/libexpat-10/job/e98ai0uf5wu5vmde#L269 Complex projects with a lot of dependencies are no problem as well. See for instance the build log of ImageMagick for Windows: https://ci.appveyor.com/project/Jan-E/imagemagick-windows/build/job/ef3gvikn64m6ddoo?fullLog=true In theory, httpd and all of its dependencies could be built as well on a Appveyor virtual Windows machine. I do not have the time to do that right now, but if anyone feels inclined... -- Jan
