On 06/27/2011 12:00 PM, John Dulaney wrote:
Ok, the current ChangeLog is up (1).
What I'm thinking is two things:
It may be a good idea to modify the script at (2) to automagically replace 'Ticket
#x'
with the ticket URL. Of course, that would require that from now on, that specific
format
for referencing the tickets will be a must.
The other thing I'm considering is how to automate ChangeLog creation. Maybe add
the
script to the server and include running it in the merge to master process? The issue
becomes how to include the ChangeLog in the Git repository, but make it so that the Git
log doesn't wind up getting ChangeLog modified type messages. Maybe just not git
add
the file in the master? But then, how to keep the ChangeLog when master is cloned?
Cool, I assume that was all generated using the script you linked to?
I guess I was thinking of something different for the NEWS/ChangeLog
than that - just something describing the high-level changes to the
project since the last release instead of a description of all the commits.
I'm not sure there is a whole lot of utility out of keeping messages
like these in a file:
Kamil Páral <kparal(a)redhat.com> 2011-06-13
pretty_log: colorize result
Tim Flink <tflink(a)fedoraproject.org> 2011-06-10
detect python version in runtests.sh instead of assuming 2.7
Tim Flink <tflink(a)fedoraproject.org> 2011-06-10
removing finally block that doesn't work on el5
James Laska <jlaska(a)redhat.com> 2011-06-10
More missing BuildRequires
If someone really wanted that level of detail, I think that git log
would be a much better route (easier to filter, colorized, customizable
etc.).
Thoughts?
Tim