hi Derick, On Sun, Mar 3, 2013 at 8:00 PM, Derick Rethans <der...@derickrethans.nl> wrote: > Hi, > > I've just renamed the NEWS files to a branch specific variant. NEWS > files should not be merged up (as their contents are not linked) and > they always cause a bit pain when doing automated things (such as the > tzdb update).
Commit first and then ask (well, inform us in this case...) is not going to work very well. About this issue, there are different problems to solve. If developers does not setup his git correctly, then we have to make the points listed in the FAQ more visible. Maybe on www as well, or at least a link with "Please configure git correctly as described in...". Also not only NEWS should be there but the various UPGRADING files as well. That's something you would notice as soon as you implement new things. 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. Cheers, -- Pierre @pierrejoye -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
