Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62941 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66565 invoked from network); 11 Sep 2012 05:47:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Sep 2012 05:47:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.153 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.153 smtp153.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.153] ([67.192.241.153:53198] helo=smtp153.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D0/86-33014-870DE405 for ; Tue, 11 Sep 2012 01:47:37 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp15.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 40CFB300436; Tue, 11 Sep 2012 01:47:34 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp15.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 9098E300449; Tue, 11 Sep 2012 01:47:33 -0400 (EDT) Message-ID: <504ED075.9010200@sugarcrm.com> Date: Mon, 10 Sep 2012 22:47:33 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Pierre Joye CC: Nikita Popov , Rasmus Lerdorf , Anthony Ferrara , jpauli , PHP Internals References: <504E4568.4030701@lerdorf.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] What is our definition of a "Backward Compatibility Break" From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > We do not have this clue in master and there are for sure non > acceptable BC breaks in master. They won't be in 5.5. I'd said before, Why don't we have a clue? We definitely do have a clue, we have git logs and we know what went into master - it is not that old. Could you list the non-acceptable BC breaks that are now in 5.5? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227