On quarta-feira, 17 de julho de 2013 21.45.11, Giuseppe D'Angelo wrote: > I 100% agree with having the changelog entry in the commit message, > but I fear the complexity there. We should try to work towards > error-proof entries -- I fear that too many people will mispell > "Important Behavior Changes" or similar, causing frustation when the > sanity bots complains.
I don't see that a problem. I can do a case-insensitive comparison when grouping and the changelog is meant to be proof-read by a human anyway. Also, don't forget we have a Rohanbot that is doing spellchecking. > Can we devise something simpler? Can we also put in our policies an > example of how a changelog file is structured, and what are the right > tags to use to add an entry to a given section? "Use the tags that appear in the changelog file" -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
