Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52652 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67329 invoked from network); 1 Jun 2011 11:19:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 11:19:30 -0000 Authentication-Results: pb1.pair.com header.from=johncrenshaw@priacta.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=johncrenshaw@priacta.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain priacta.com designates 64.95.72.238 as permitted sender) X-PHP-List-Original-Sender: johncrenshaw@priacta.com X-Host-Fingerprint: 64.95.72.238 mx1.myoutlookonline.com Received: from [64.95.72.238] ([64.95.72.238:9196] helo=mx1.myoutlookonline.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D7/01-61684-14026ED4 for ; Wed, 01 Jun 2011 07:19:30 -0400 Received: from st21.mx1.myoutlookonline.com (localhost [127.0.0.1]) by mx1.myoutlookonline.com (Postfix) with ESMTP id 289B8553C23 for ; Wed, 1 Jun 2011 07:19:27 -0400 (EDT) X-Virus-Scanned: by SpamTitan at mail.lan Received: from HUB015.mail.lan (unknown [10.110.2.1]) by mx1.myoutlookonline.com (Postfix) with ESMTP id 95718553AA1 for ; Wed, 1 Jun 2011 07:19:26 -0400 (EDT) Received: from MAILR001.mail.lan ([192.168.1.2]) by HUB015.mail.lan ([10.110.17.15]) with mapi; Wed, 1 Jun 2011 07:18:17 -0400 To: PHP internals Date: Wed, 1 Jun 2011 07:19:22 -0400 Thread-Topic: [PHP-DEV] Final version, RFC release process Thread-Index: AcwgTBRs3tVBkLD/QDSQYbKklYnyWQAAD88A Message-ID: References: <4DE61D77.7040506@zend.com> In-Reply-To: <4DE61D77.7040506@zend.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: [PHP-DEV] Final version, RFC release process From: johncrenshaw@priacta.com (John Crenshaw) That isn't measurable, so it is a suggestion, not a standard. It also creat= es serious problems in userland if APIs change. API changes lead hosts to l= iterally take years to update to new versions of PHP, for fear of breaking = the sites that host with them. What about: Userland API compatibility of documented interfaces and behaviors must be k= ept. API internals should be backwards compatible wherever possible. This relaxes the userland restriction just slightly to allow for changes th= at break undocumented behaviors, but leaves it basically stable and measura= ble. This also leaves the door open for internal changes if they're really = needed, but basically suggests against it. John Crenshaw Priacta, Inc. -----Original Message----- From: Dmitry Stogov [mailto:dmitry@zend.com]=20 Sent: Wednesday, June 01, 2011 7:08 AM To: Pierre Joye Cc: PHP internals Subject: Re: [PHP-DEV] Final version, RFC release process Hi, In my opinion a restriction "API compatibility must be kept (internals=20 and userland)" for x.y.z to x.y+1.z is too strict. It just can block=20 some new features forever. I would suggest to change "API compatibility must be kept" to "API=20 backward compatibility must be kept as much as possible". Thanks. Dmitry.