Bug #89910 for Shell-Cmd: Skeleton Changes file for your dist

Wed Oct 30 18:14:57 2013 NEILB [...] cpan.org - Ticket created

Subject:

Skeleton Changes file for your dist

Hi Sullivan, Attached is a skeleton Changes file for this dist, that conforms to CPAN::Changes::Spec. Following this format means that various tools can more easily process your distribution automatically. For example MetaCPAN will display the most recent changes with your dist. You can find out more about this at Brian Cassidy's CPAN::Changes Kwalitee Service (http://changes.cpanhq.org), which is where I saw your module listed :-) Cheers, Neil

Subject:

Changes

Download Changes
application/octet-stream 116b

Message body not shown because it is not plain text.

Thu Oct 31 10:31:00 2013 sbeck [...] cpan.org - Correspondence added

I guess I'm not seeing the vision of why a Changes file spec is all that important.... however, it's a simple enough change, so I'm trying it for this module. The one thing that wasn't clear from the spec was whether the versions had to be listed in reverse order with the oldest at the bottom. All of the examples listed them newest first, but it never stated that that was required for a valid Changes file. I do not generally care for that order (though I understand why some people do), and all of my changes files are in the order newest last. So, if the spec accepts the newest last order, I'll likely change all of my modules to this format (except for Date::Manip... there the changes are documented in detail in a whole separate POD file) since it's an easy change in that case. If on the other hand the spec can't handle this, I doubt that I'll change my other modules since that'll involve the task of reversing all of them (tedious) to put them in a format I like less than what is currently there.

Thu Oct 31 10:31:01 2013 The RT System itself - Status changed from 'new' to 'open'

Thu Oct 31 10:31:01 2013 sbeck [...] cpan.org - Status changed from 'open' to 'resolved'