Release 7.0.3

[rainerjung]

Many bug fixes have been backported from PHP 5.5 in the last 7 months. I think it is time for another release. Although it is possibe to use master via phpize, this does not provide all benefits of a real release like the RMs decision about the right snapshot to release, an updated package.xml file or the .reg files created by a real pecl installation.

[TerryE]

@rainerjung, the issue that you highlight is a valid one, IMO. ZendOpcache 7.0.3 is essentially the same as ext/opcache 5.5.0. We are currently at 5.5.8, and ext/opcache 5.5.8 does contain material changes compared to a 5.5.0 baseline.

IMO, locking the PECL ZendOptimizer releases to the current minor (e.g. 5.5.x) releases is probably overkill, but we should at least rebaseline PECL ZendOptimizer every 6 months or so. The challenge here for the Zend team is one of resourcing and priorities. Their current focus is on PHP 5.6 features and functionality. I am not sure that they see the PECL extension as more that a transitional offering, but that is only my reading.

However, I feel that keeping the PECL version reasonable current is important. Some 99% of PHP websites run PHP versions earlier than 5.5. The development project is becoming increasingly detached from the user population. I see OPcache as an important enhancement technology and we should keep it regularly updated. Maybe one approach would be for the Zend team to share maintenance of the PECL version with the community.

[rainerjung]

As far as I can see the current head of ZendOpcache is near identical to the head of 5.5 ext/opcache (so even newer than 5.5.8). The last release was 7.0.2 - outdated - and the next should be 7.0.3 which would then be mostly the latest 5.5 version with tiny adjustments.

The only deltas to the 5.5. head of ext/opcache I can currently see are:

• some additional files, mostly package.xml, opcache.ini, LICENSE, .gitignore, .travis and .travis.yml.
• some skips in a couple of tests which depend on PHP version
• additional opcache.file_update_protection=0 or opcache.validate_timestamps=1 in some tests
• one test change -$file = dirname(FILE) . "/bug6559.inc.php"; +$file = DIR . "/bug6559.inc.php";
• two conditional lines with PHP API version check

  if ZEND_EXTENSION_API_NO > PHP_5_5_X_API_NO

  in file Optimizer/block_pass.c

• a comment typo fix in the same file

That's it.

I don't see a need to include changes from the 5.6 branch. Keeping it up-to-date with 5.5 should be good enough.

Regards,

Rainer

[TerryE]

Yes, I agree that the current head of this github repository is pretty much the same as that of PHP 5.5, but this isn't the same as PECL 7.0.3. What I am suggesting is that every ~6 months, we do a dot release of PECL ZendOpcache to resync to the current release. Soon after the release of 5.6, then we should rebaseline 7.1.x which is aligned to the 5.6 functionality.

[laruence]

7.0.3 is released