I'd like to see https://github.com/php/php-src/pull/694 / https://github.com/php/php-src/pull/765 in so FPM in 5.4 will work properly with Apache 2.4.10+'s mod_proxy_fcgi.
David On 19 Aug 2014, at 01:59, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > > Moving this out of other topics into its own: according to the release > RFC, we should have 5.4 have 2 years of bugfixes & one year of security > fixes. Since 5.4 was released in March 2012, we're already past 2 year > mark. However, we're still have some bugfixes in 5.4, so I'd like to do > this: > > - 5.4.32 is released as planned this week, nothing changes there. > > - 5.4 branch that is to be 5.4.33 will be the last release that has any > non-security bugfixes. We hope that by the time 5.4.33 is out 5.6.0 is > out too, so that would play nice with the "two stable branches, one > security branch" theme. Starting from that release forward, 5.4 would be > purely security fixes only branch. > > - EFFECTIVE IMMEDIATELY, we do not accept new non-security bugfixes into > 5.4 branch unless they are very important ones (and that is only because > people may, in theory, have pending patches and we didn't give advance > notice). Importance would have to be determined somewhat arbitrarily, > but basically if it works without it, then it's not in, if there's > serious doubt if it should be in, it's not in, etc. Security issues, of > course, still allowed in. > > This means if somebody has some pending non-security fixes that have to > be in 5.4, the following two weeks are the last call, provided that the > fixes really must be in 5.4. > > Any objections/suggested modifications to this plan? > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
