My biggest concern is blocking merges on badly formatted release notes. I
see this all the time with core and the merge conflicts associated due to
multiple people editing the text file.
If we can have a tool that generates these consistently I'm all for release
notes. Versioning seems like a no brainer but I'd rather have no release
notes than bad release notes.
On Tue, Mar 24, 2015 at 10:42 AM, Sam Smith <samsmith(a)wikimedia.org> wrote:
Seems sensible, but knowing history I don't think
it will be updated
correctly.
We're a different team now. Whaddya say we give it a try?
I think the updating of VERSION.txt really needs
to be automated. Can we
have a script that can be run bumps the version number and generates these
logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this
list. I think without this, this is a nice idea but will be disastrous.
https://github.com/tj/git-extras/wiki/Commands#git-changelog is one of
the many solutions to this turned up by a quick Google :)
–Sam