Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93916 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38815 invoked from network); 12 Jun 2016 18:43:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jun 2016 18:43:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 77.244.243.86 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 77.244.243.86 mx105.easyname.com Received: from [77.244.243.86] ([77.244.243.86:36655] helo=mx207.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8F/23-12403-46DAD575 for ; Sun, 12 Jun 2016 14:43:49 -0400 Received: from cable-81-173-133-15.netcologne.de ([81.173.133.15] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1bCAMK-0004al-SC; Sun, 12 Jun 2016 18:43:45 +0000 Reply-To: internals@lists.php.net References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> <027a527e-0920-9e57-b2cc-60fcbfedb84e@gmail.com> To: Rowan Collins , PHP Internals Message-ID: <6365af8f-a2b5-4a04-c312-88f91b35e3f7@fleshgrinder.com> Date: Sun, 12 Jun 2016 20:43:38 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <027a527e-0920-9e57-b2cc-60fcbfedb84e@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="aUMVRCwAH3dqKfn3tuK0axeNuhtiOArJj" X-ACL-Warn: X-DNSBL-BARRACUDACENTRAL Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? From: php@fleshgrinder.com (Fleshgrinder) --aUMVRCwAH3dqKfn3tuK0axeNuhtiOArJj Content-Type: multipart/mixed; boundary="tb4rob3xKGNptIj5RmoHjBTNOUXOrP8CB" From: Fleshgrinder Reply-To: internals@lists.php.net To: Rowan Collins , PHP Internals Message-ID: <6365af8f-a2b5-4a04-c312-88f91b35e3f7@fleshgrinder.com> Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> <027a527e-0920-9e57-b2cc-60fcbfedb84e@gmail.com> In-Reply-To: <027a527e-0920-9e57-b2cc-60fcbfedb84e@gmail.com> --tb4rob3xKGNptIj5RmoHjBTNOUXOrP8CB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 6/12/2016 8:21 PM, Rowan Collins wrote: > A policy of "every BC break should be analysed as a cost-benefit > tradeoff" might perhaps be a better one than we have now; it is not, > however, what is written in the Release Process RFC. >=20 Which would be arbitrarily laid out anyways. Think of the var keyword deprecation RFC. It was random, it is random, and it will be random I guess. --=20 Richard "Fleshgrinder" Fussenegger --tb4rob3xKGNptIj5RmoHjBTNOUXOrP8CB-- --aUMVRCwAH3dqKfn3tuK0axeNuhtiOArJj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXXa1eAAoJEOKkKcqFPVVr8sAP+wR0rAEl+98ZC3De2pZZJUsZ mZSRbBjpl6e/KWhB7exrR9Z8ViqxIZ9GFzv/R/NM81I8/sEq1zY0yZJq2QqjKYUQ dLMRZstHYLS0MApFM8JP7pqQ9B/KcJ2icogIa1CzCdSOGACrtFzJdC09Inn7TrXg lk23Fync78EQFf3LLGX7B5LIS3TKZ4NQU1qYvDngYCk59QJCYEX4qRF9hYmj0/uL IBNMderq/qK2z/K5m0IQqNDT9P6h/V70ydtbXTnUwHQgHUPGLIasMkV9fsKOPz4c U9eadQX/GrQiQwX4r+ZLSM6GEytoyy53mvgWs2mFBk2X5p1pQ7OZXNWIDQJh7TEO aM9sBC2/8MATRN7GXDCuR44rLfSgqfcDy6qEhCTgpvMff5WeV3jMj+ndPQ32UbPP lXA7R5sbWKZga1fTCgmWYKDAIyKjLJc+ek/t+8ed+MOi+rT/GUEkxEWdf29GFH5H 4EzoUel4OUwfbsDKzCU9VvBRHT68lsDPSHE1+9pTvFhKksaCAkb3vrdSXZMKtWPD r1bPQXwlWcEhxxuaI9ZfVPcabmlzIrQeUkNBoVEyIaHgCLlxEOA04bJFep1yEZPP v0Ct5nGdtWOiW88itPPKLIMYkv2Dfxfwv7aZSOzsScNug4cNw3/nAVpKZkmryZZG FDUFzs04GlYGCE9jAtrj =VyM2 -----END PGP SIGNATURE----- --aUMVRCwAH3dqKfn3tuK0axeNuhtiOArJj--