Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59221 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41848 invoked from network); 30 Mar 2012 07:27:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Mar 2012 07:27:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=glopes@nebm.ist.utl.pt; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=glopes@nebm.ist.utl.pt; sender-id=unknown Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error) X-PHP-List-Original-Sender: glopes@nebm.ist.utl.pt X-Host-Fingerprint: 193.136.128.22 smtp2.ist.utl.pt Linux 2.6 Received: from [193.136.128.22] ([193.136.128.22:35467] helo=smtp2.ist.utl.pt) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 23/04-17229-050657F4 for ; Fri, 30 Mar 2012 02:27:13 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.ist.utl.pt (Postfix) with ESMTP id DF2F6700048C; Fri, 30 Mar 2012 08:27:08 +0100 (WEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at ist.utl.pt Received: from smtp2.ist.utl.pt ([127.0.0.1]) by localhost (smtp2.ist.utl.pt [127.0.0.1]) (amavisd-new, port 10025) with LMTP id OL7A0K0Qkd8m; Fri, 30 Mar 2012 08:27:08 +0100 (WEST) Received: from mail2.ist.utl.pt (mail.ist.utl.pt [IPv6:2001:690:2100:1::8]) by smtp2.ist.utl.pt (Postfix) with ESMTP id 90B55700048B; Fri, 30 Mar 2012 08:27:08 +0100 (WEST) Received: from slws007.slhq.int (a79-168-248-114.cpe.netcabo.pt [79.168.248.114]) (Authenticated sender: ist155741) by mail2.ist.utl.pt (Postfix) with ESMTPSA id A7DCC2004F8F; Fri, 30 Mar 2012 08:27:07 +0100 (WEST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "PHP Internals" , "Stas Malyshev" References: <4F755AFC.2040101@sugarcrm.com> Date: Fri, 30 Mar 2012 09:27:06 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?= =?utf-8?Q?ca_do_I=2ES=2ET=2E?= Message-ID: In-Reply-To: <4F755AFC.2040101@sugarcrm.com> User-Agent: Opera Mail/11.61 (Win32) Subject: Re: [PHP-DEV] PHP 5.4.1 RC1 Released From: glopes@nebm.ist.utl.pt ("Gustavo Lopes") On Fri, 30 Mar 2012 09:04:28 +0200, Stas Malyshev wrote: > The full list of the fixes is as always in the NEWS file. > I'm afraid it isn't. You did not merge the changes from 5.3 NEWS to 5.4. I know this is controversial and some people have been committing to both 5.3 and 5.4 NEWS files. However, we have clear guidance for this: 70 3. All news updates intended for public viewing, such as new features, 71 bug fixes, improvements, etc., should go into the NEWS file of the 72 *first* to be released version with the given change. In other words 73 any NEWS file change only needs to done in one branch. http://git.php.net/?p=php-src.git;a=blob;f=README.SVN-RULES;h=de9d27490aecee211c07b6f6ee861d52d9f74ea9;hb=babe3ee0d2ba4f6c919bbb6710f232e6ef91e6ac#l70 As far as I remember, this was observed in the 5.2 era. I think it would make more sense to change this rule and update all NEWS files for stable branches as it would alleviate the RMs from the work of determining which of the changes were 5.3 only, but either way we ought to stick to one uniform rule. The status quo (some people updating one NEWS file, others updating both) is not very satisfactory. -- Gustavo Lopes