Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48566 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 864 invoked from network); 29 May 2010 12:06:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 May 2010 12:06:55 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 unknown Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:33579] helo=schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/F1-19421-353010C4 for ; Sat, 29 May 2010 08:06:44 -0400 Received: from localhost (ka.local [127.0.0.1]) by schlueters.de (Postfix) with SMTP id 719DE2507D for ; Sat, 29 May 2010 14:06:40 +0200 (CEST) Received: from [192.168.1.33] (ppp-93-104-125-33.dynamic.mnet-online.de [93.104.125.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by schlueters.de (Postfix) with ESMTPSA id 223C52507B; Sat, 29 May 2010 14:06:40 +0200 (CEST) To: Pierre Joye Cc: PHP internals list In-Reply-To: References: <1275052922.23351.292.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Date: Sat, 29 May 2010 13:17:25 +0200 Message-ID: <1275131845.2609.8.camel@guybrush> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] ChangeLog From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hey, On Fri, 2010-05-28 at 23:50 +0200, Pierre Joye wrote: > I'd to add that unless we add everything in the NEWS file, the > ChangeLog remains the only way to have a list of all changes (without > doing manually). Having the file is absolutely fine with me, while I can fulfill my needs with svn annotate and svn log. But if we ship it, it should be correct and at least since 5.2.0 we ship a wrong (not updated) file. And that I consider bad. So I ask somebody to either remove it or make sure it's updated (automatically or by adding instructions to README.RELEASE_PROCESS) in all places. johannes