I know they have been testing it and found no incompatibilties. But chances are high that I will be running a dual setup with PHP 5.3 as mod_php and PHP 7.0 as mod_fcgid very soon (like I do now with 5.3 & 5.6). In a dual setup I'd like to use the same OpenSSL version. Mixed VC9 and VC14 binaries are not my favourite either, but I've learned to deal with VC9/VC11 as well.

And besides that: PHP 5.3 is already out-of-support. Support for version 0.9.8 will cease on 2015-12-31. No further releases of 0.9.8 will be made after that date. The least I can do is compile the older PHP versions with a supported OpenSSL version.

Although PHP 7.0.0 has not been released yet (and there are discussions on what will be the best timing for the release), PHP 5.6 is still scheduled to enter 'security fixes only' in 9 months from now:
http://php.net/supported-versions.php

Maybe this will be extended somewhat, given that PHP7 was not released within a year after the release of PHP 5.6. But the EOL of OpenSSL 1.0.1 will not be postponed, so there is every reason to upgrade the OpenSSL version in PHP 5.6 to 1.0.2 within the coming year.

Version 5.6.16 is available. Please keep in mind that all my builds use OpenSSL 1.0.2-fips now, while php.net uses OpenSSL 0.9.8 for 5.3 & 5.4 and OpenSSL 1.0.1 for 5.5 & 5.6. Be careful when mixing my extensions with the official binaries.

I will wait with compiling it, because December 3rd is the official release date. December 3rd is also the release date of the next OpenSSL versions. And December 2nd is the release date of the next cUrl version.

The inconvenience of the release lateness in several time zones is caused by the need to ensure the compatibility with the latest OpenSSL 1.0.2e release. Thanks for the patience!

It is not just a next major PHP version being released today. The release being introduced is an outcome of the almost two years development journey. It is a very special accomplishment of the core team. And, it is a result of incredible efforts of many active community members. Indeed, it is not just a final release being brought out today, it is the rise of a new PHP generation with an enormous potential.

Upgraded all my builds from ICU-55 to ICU 56.1, the version php.net uses for PHP7. Be sure to add the icu*56.dll's to all appropiate places (like the php-dir and apache24\bin) if you use the php_intl.dll from my builds.

Upgraded php_av.dll (PHP 5 only) to use avcodec-57, avformat-57, avutil-55, swscale-4 and swresample-2. Not that I expect anyone to use this extension anymore, because it is not maintained. With some troubles I got a PASS on 11 of the 13 tests.

Upgraded to fribidi 0.19.7, freetype 2.6.2 (in php_gd2.dll) and more of the same.

Thanks for your efforts Jan, I always snatch your extensions and combine them with the official binaries
Working great so far!

One thing I'd like to ask you: how do I get the build to compile as x64? I need the xxhash extension and successfully built PHP 7.0.3 x86 but can't figure out how to set up the compiler environment for x64.

Opening the 'VS2015 x64 Native Tools Command Prompt' should be enough to achieve 64-bits compilation of PHP7. And you will need to clone https://github.com/nheimann1/php-xxhash because only this one seems to have 64-bits support.

I cloned develop, as develop has php7 merged. The additional commit on develop are just some README changes.

I tested the compiled x86 and x64 dlls and hashes seem identical between both php7 installs.

Guess I'll have to compare the code of both extensions and see what the main differences are... I've already noticed that Megasaxon's version outputs strings instead of integers, which saves some application-side conversions in my case (had to do dechex() before).