Hi! > Debian, Ubuntu and CentOS: ~21,23% > > (I assume here like Anthony that the installs matching a distribution > specific version always come from that distribution).
Pretty big one, I'd say, but even with this one you only get 1/5. Also, as I said, it's very easy to take distro package and repackage it to use the source from the same minor but up-to-date patch version. > An addition and a bug fix are different things. I know but you said, I'm quoting, "please let the x.y.z versions contain only additional (security) fixes" which excluding non-security fixes too. Let's consider a somewhat arbitrary example: https://github.com/php/php-src/pull/1211 There's a HTTP status code needs to be added (doesn't matter if new or just omitted by oversight). You could have it in next 5.6 version (you can have it in use in 3 months realistically - one month for release to catch up, 2 months for ops in your project to be confident that new patch release doesn't break anything) or you could have it in 2.5 years (1.5 years for 7.1 to be released, 1 year - and that's *extremely* optimistic - for ops to be ok to switch to a new distro version which hopefully - just hopefully, extremely optimistic again - but that time ships with 7.1 and not still randomly patched 5.5). For me, it sounds insane that you'd have to wait for so long for such a simple thing. Of course, instead of status code it could be option support in XML, or new function/option support in ICU, or new connection option in mysql. Any improvement in the environment - do you want it in PHP in terms of several years or in terms of 3 months? I foresee what it would turn into is arguing "well, not supporting option X is really a bug so that's a bugfix!" which only will lead to more chaos and argument. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
