On Thu, Nov 17, 2011 at 10:39:32AM -0800, Josh Susser wrote: > I suggest using git-notes to mark commits for the CHANGELOG. Metadata FTW! > > Not all changes are worth mentioning in the CHANGELOG. But with git-notes, > you can annotate commits with additional comments after the commit is made. > You can tag commits that you want in the CHANGELOG and then assemble the > CHANGELOG by a script in any fashion you want. You can even see these notes > on GitHub: > > https://github.com/blog/707-git-notes-display > > I don't know if you'd want to just tag the commits or add extra information > for the CHANGELOG entry, but I'm sure the core team can figure out how they > want to manage that.
Git notes don't buy us much because a revert will not remove the note. The release manager (or the script we write) would have to reconcile reverted commits before assembling the changelog: [aaron@higgins fooo (master)]$ git log commit 94cf5f7c933bd9590ce5b284a6470c3a142de5b2 Author: Aaron Patterson <[email protected]> Date: Fri Nov 18 09:09:18 2011 -0800 Revert "world commit" This reverts commit b2d80645225e9ba9cc83a373eb596ec976bed7fb. commit b2d80645225e9ba9cc83a373eb596ec976bed7fb Author: Aaron Patterson <[email protected]> Date: Fri Nov 18 09:08:44 2011 -0800 world commit Notes: my first note commit 948a3c07d1f9f867ab62047daff39c412a05946b Author: Aaron Patterson <[email protected]> Date: Fri Nov 18 09:07:40 2011 -0800 first commit [aaron@higgins fooo (master)]$ -- Aaron Patterson http://tenderlovemaking.com/
pgp5RwOKiTg3v.pgp
Description: PGP signature
