Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66461 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90177 invoked from network); 4 Mar 2013 06:23:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Mar 2013 06:23:22 -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.203 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.203 smtp203.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.203] ([67.192.241.203:56692] helo=smtp203.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F6/13-04779-9DD34315 for ; Mon, 04 Mar 2013 01:23:22 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp20.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 88628258337; Mon, 4 Mar 2013 01:23:18 -0500 (EST) X-Virus-Scanned: OK Received: by smtp20.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 08BD82580A9; Mon, 4 Mar 2013 01:23:17 -0500 (EST) Message-ID: <51343DD5.40002@sugarcrm.com> Date: Sun, 03 Mar 2013 22:23:17 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: Pierre Joye CC: Derick Rethans , PHP Developers Mailing List , David Soria Parra References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] NEWS file rename From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I'd to agree on one thing tho'. NEWS should not be manually edited. > With or without git, it is a (relatively small) pain. Back to the git > migration time, David and I discussed about generating it from the > commit messages. That implies to enforce a commit message format, a > 1st attempt is described here: > https://wiki.php.net/vcs/gitworkflow#new_commit_message_format. The > RMs could then call a script to generate it on release. Commit messages themselves won't be very useful - a fix could include a number of commits, and people regularly write commit messages not in format suitable for NEWS. I'd rather prefer them to put it in NEWS file - where they have an example of how it's done right, and where they can put it in proper order, proper sections, etc. It won't save much work because if people would neglect to do it with NEWS file, they'd also neglect to put messages in commit in proper format, so they will have to be hand-edited anyway. So we don't win much by telling people not to bother about NEWS anymore - I'd rather have them to bother with it and make RM's life a bit easier. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227