Re: Adding NEWS entries to each active stable release branch (was: NEWS handling)

On Wed, Oct 16, 2013 at 6:02 PM, Pierre Joye <pierre.php@gmail.com> wrote: > On Wed, Oct 16, 2013 at 3:23 PM, Johannes Schlüter > <johannes@schlueters.de> wrote: > > > Ideal would be a tool where an RM can invoke a script which parses > > commit messages and builds NEWS from there. This requires some stricter > > rules on commit message formats, though. (the idea is as old as the git > > migration but there wasn't a good idea, yet) > > Yes, that's the idea behind the new commit message format: > > https://wiki.php.net/vcs/gitworkflow#new_commit_message_format > > But somehow even harder to enforce. > I think it's pretty hard to get this information from the commit messages (not all commits are NEWSworthy, some changes have multiple commits). Maybe it's better to integrate this with bugs.php.net? After all NEWS only has changes with assigned bug IDs (minus rather rare exceptions), so that seems like a good place to do it. I.e. don't just "Closed" the bugs, but make them "Fixed in PHP 5.4.20, PHP 5.5.5" or something. Just a thought, not sure if it makes sense. Nikita