That's a great idea Mike. I like that better than any of the ideas I've heard so far. There is still some discipline required -- every substantial commit must address a ticket -- but that's a good practice anyway.
On Tue, May 31, 2016 at 7:50 PM, Mike Dewhirst <[email protected]> wrote: > On 1/06/2016 6:12 AM, Ryne Everett wrote: > >>  ### Why can’t people just use a `git log` diff? >> >> Because log diffs are full of noise — by nature. They could not >> make a suitable >> change log even in a hypothetical project run by perfect humans who >> never make >> typos, never forget to commit new files, never miss any part of a >> refactoring. >> The purpose of a commit is to document one atomic step in the process >> by which >> the code evolves from one state to another. The purpose of a change >> log is to >> document the noteworthy differences between these states. >> >> > We use Trac for ticketing and modified the ticket to include a custom > field called, wait for it ... "Release note" ... which is filled in when > the ticket is written. It contains the exact words the ticket writers want > used when release notes are compiled. > > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
