Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76697
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.176 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <53F29345.40607@sugarcrm.com>
Date: Tue, 19 Aug 2014 12:58:47 +0200
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <FB948124-9042-4CCA-B698-3FCED176393D@heroku.com>
References: <53F29345.40607@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] 5.4 security only
From: dz@heroku.com (David Zuelke)

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 <smalyshev@sugarcrm.com> wrote:

> Hi!
>=20
> 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:
>=20
> - 5.4.32 is released as planned this week, nothing changes there.
>=20
> - 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.
>=20
> - 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.
>=20
> 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.
>=20
> Any objections/suggested modifications to this plan?
> --=20
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20