Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60876 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26249 invoked from network); 18 Jun 2012 06:01:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jun 2012 06:01:28 -0000 Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.199.177.89 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 212.199.177.89 il-mr1.zend.com Received: from [212.199.177.89] ([212.199.177.89:50056] helo=il-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/3C-49496-634CEDF4 for ; Mon, 18 Jun 2012 02:01:27 -0400 Received: from il-gw1.zend.com (unknown [10.1.1.22]) by il-mr1.zend.com (Postfix) with ESMTP id 5D8D36064F; Mon, 18 Jun 2012 08:54:58 +0300 (IDT) Received: from tpl2.home (10.1.10.6) by il-ex2.zend.net (10.1.1.22) with Microsoft SMTP Server id 14.1.255.0; Mon, 18 Jun 2012 09:01:18 +0300 Message-ID: <4FDEC434.506@zend.com> Date: Mon, 18 Jun 2012 10:01:24 +0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Stas Malyshev CC: Laruence , PHP Internals References: <4FDD6CED.9060704@sugarcrm.com> In-Reply-To: <4FDD6CED.9060704@sugarcrm.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.1.10.6] Subject: Re: what is the rule of merging fix to release branch? From: dmitry@zend.com (Dmitry Stogov) On 06/17/2012 09:36 AM, Stas Malyshev wrote: > Hi! > >> there comes some bug of a already fixed issue (PHP5.4.4) >> >> the fix(#61998) is here >> https://github.com/php/php-src/commit/90e23107a2acba1fd53b7e799372eb9f24194a56 >> >> but seems this fix is not merged into 5.4.4 when it was released? >> >> so, what is the rule? :) > > The fixes are merged into 5.4 branch (never in release branches). > Releases are regularly started from 5.4. Next one will be started in 2 > weeks. This fix was committed on 2012-05-21, so I'm surprised why it's not included into release. Thanks. Dmitry.