Closed kentfredric closed 6 years ago
I modified the changelog. Since the changes are written in YAML format, I prefix the issues/PRs with PR#number
or Issue#number
to avoid having to quote it. It's still turned into links on metacpan.
I added information to the PRs where it was missing.
Will be in the next version.
As a maintainer is very furstrating reading a changelog and seeing:
Most of this is because many people reference PR's without giving a summary, and that's very confusing, and this looks like that, where you've interspersed "fixed PR X" lines with other fixes, leaving me wondering "ok, so what is PR/171?!?!" and having to look it up.
Except in your case, it turns out you're using 2-lines per entry with seperate bullet points.
I'd propose something clearer like:
The idea being to give the most relevant information first, and encourage people only to dig if the relevant information is insufficient.
Also, note in my example I stripped "issue/" and "PR/", mostly because github uses a single sequence for both, and all those prefixes do is impede the ability for MetaCPAN to reference your ticket.
An alternative idea might also be:
The approach here trying harder to group related entries and only have a bullet point per entry.