Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62766 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50082 invoked from network); 3 Sep 2012 21:58:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Sep 2012 21:58:05 -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.113 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.113 smtp113.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.113] ([67.192.241.113:49579] helo=smtp113.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/3A-20751-CE725405 for ; Mon, 03 Sep 2012 17:58:05 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp21.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id D17712403F8; Mon, 3 Sep 2012 17:58:01 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp21.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 89D3E2403A9; Mon, 3 Sep 2012 17:58:01 -0400 (EDT) Message-ID: <504527E8.2010900@sugarcrm.com> Date: Mon, 03 Sep 2012 14:58:00 -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: PHP Internals References: <5042C04A.2040104@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Release scheduling, branching & NEWS for 5.4 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > And no BC in 5.5 as well. Which will cause us some issue for 5.5 as > master actually has BC breaks as far as I remember. We accept binary API changes in 5.5, but only very slight PHP-level API changes (such as removal of functions like logo GUIDs). Another important point - any such change that may influence PHP developers should be in UPGRADING file. Including adding functions, arguments, options, etc. - this will help to keep it properly documented too. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227