Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59224 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48940 invoked from network); 30 Mar 2012 07:53:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Mar 2012 07:53:01 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 173.203.6.139 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 173.203.6.139 smtp139.ord.emailsrvr.com Linux 2.6 Received: from [173.203.6.139] ([173.203.6.139:49596] helo=smtp139.ord.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 86/95-17229-B56657F4 for ; Fri, 30 Mar 2012 02:53:00 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp19.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 98C091C0082; Fri, 30 Mar 2012 03:52:57 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp19.relay.ord1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 43AFD1C007F; Fri, 30 Mar 2012 03:52:57 -0400 (EDT) Message-ID: <4F756658.3040102@sugarcrm.com> Date: Fri, 30 Mar 2012 00:52:56 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Gustavo Lopes CC: PHP Internals References: <4F755AFC.2040101@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.4.1 RC1 Released From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > 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: OK, we need to have specific policy on it, because I'm hearing people having contradictory opinions on that. > 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. I know, I will update NEWS for final release, but I want to know what policy we adopt - "lowest version" NEWS or "all stable branches" NEWS? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227