Re: NEWS file rename
| From: | Pierre Joye | Date: | Mon, 04 Mar 2013 06:27:23 +0000 |
| Subject: | Re: NEWS file rename | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-66462@lists.php.net to get a copy of this message | ||
On Mon, Mar 4, 2013 at 7:23 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> 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,
Well, we could write a pre commit script and reject commits with
invalid messages, hard but fair :)
Cheers,
--
Pierre
@pierrejoye