Changes File How-To Follow-Up

My last post on Changes files purported to be both a how-to and how not-to, but I got a bit carried away with the how not-to part. Several comments since that post made excellent points, so here’s the summary.

Kent Fredric says “don’t be lazy and just copy the output from “git log” into your Changelog.” Yes, a thousand times yes! Remember, the Changes file is for end users of your library, and we don’t care about all the little details. Just give us the summary. (Ok, that’s the last how not-to.)

RJBS says “put the latest release at the TOP of the file.” Yes, we’re talking to you, Damian. When I open up the Changes file I don’t want to read about the first release from three years ago.

On #moose IRC, Karen Etheridge also mentioned the importance of linking changes to tickets. The Dancer file I criticized was already doing that, and I meant to highlight that, but got caught up in ranting. All you need is the ticket id and the relevant system, something like “RT #12345” or “GH #456” at the end of a particular change.

Karen also suggested mentioning the commit id in the changes file. I’m not so sure about that. I’d rather see some sort of integration between the bug tracker and the source control system. I’ve used such systems at several jobs. I would write “RT 12345” in my commit message, and that commit message would be appended to the ticket as a comment.

Updated on

One thought on “Changes File How-To Follow-Up

  1. To clarify, I don’t think the commit id should be in the changes file, but it definitely belongs in the bug tracking ticket. That way anyone coming long later reading about the bug can find the exact code that fixed the bug – it’s possible the fix wasn’t complete, or a similar bug happened somewhere else, so it’s of significance to be able to see what actually was done to fix the issue.

Comments are closed.