Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58051 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80441 invoked from network); 24 Feb 2012 23:18:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Feb 2012 23:18:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=h.reindl@thelounge.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=h.reindl@thelounge.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain thelounge.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: h.reindl@thelounge.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:38650] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/E3-17132-5CA184F4 for ; Fri, 24 Feb 2012 18:18:30 -0500 Received: from srv-rhsoft.rhsoft.net (openvpn-rh.thelounge.net [10.0.0.241]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.thelounge.net (Postfix) with ESMTPSA id 6E846B0 for ; Sat, 25 Feb 2012 00:18:26 +0100 (CET) Message-ID: <4F481AC1.4060800@thelounge.net> Date: Sat, 25 Feb 2012 00:18:25 +0100 Organization: the lounge interactive design User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: internals@lists.php.net References: <4F47E90E.9040701@oracle.com> <4F47EBBE.2010202@sugarcrm.com> <4F47EEE3.90108@oracle.com> <4F47F72C.7040605@php.net> <4F47FF63.5020909@lsces.co.uk> In-Reply-To: X-Enigmail-Version: 1.3.5 OpenPGP: id=7F780279; url=http://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA99FFDCFD9EE8DBACE3CF381" Subject: Re: [PHP-DEV] Apache 2.4 support in PHP 5.4.0? From: h.reindl@thelounge.net (Reindl Harald) --------------enigA99FFDCFD9EE8DBACE3CF381 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 25.02.2012 00:09, schrieb Bostjan Skufca: > Despite the fact that Apache HTTPD's website says that 2.4.1 "represent= s > the best available version of Apache HTTP Server", and that PHP 5.4.0 w= ill > probably also bear similar notation (guesswork here!), very few (if any= !) > production environments are going to even bother considering running fi= rst > minor version of any major release. >=20 > For both, they will probably wait for 2.4.2(-5) and 5.4.1(-4) because w= ith > every major release there is a high suspicion about new bugs that may h= ave > been introduced during the development process (besides the documented > backwards compatibility breaks). >=20 > Given all above, no serious user of Apache+PHP will mind if PHP team > introduces necesary code changes into PHP between versions 5.4.0 and 5.= 4.1, > in order to support Apache Httpd 2.4.x in 5.4.x releases later on. >=20 > Again, why? Because they will skip 5.4.0 in production. And 2.4.1 too. you are missing the fact that many consider testing the new major version= s and many of them will only start testing PHP 5.4 in combination with Apac= he 2.4 why? because you have ONE big test challenge at once * httpd * httpd-extensions * php * php-extensions / pecl-extensions * your applications with both of them nobody will start consider PHP 5.4 if Apache 2.4 is on the internal roadmap before both work together because it would mean the whole work twice in other words: if both work together ASAP i wil consider both in 2012, if not both will be delayed to 2013 --------------enigA99FFDCFD9EE8DBACE3CF381 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9IGsEACgkQhmBjz394Anmg3ACfZW83uD0i3mmHJxQNEzdhWhpB lDQAniIxe2BFwXIoU6KyeJnWGhy6NxrW =01iK -----END PGP SIGNATURE----- --------------enigA99FFDCFD9EE8DBACE3CF381--