use Perl

• Module::Changes (Score:1)

  by hanekomu (8123)

  You might also want to have a look at Module::Changes [cpan.org], especially the bin/changes program.

  All my recently uploaded distros now contain YAML-based Changes files.

  I'm also checking the YAML Changes file, but do it from within shipit using ShipIt::Step::CheckYAMLChangeLog [cpan.org].
  • Re: (Score:1)

    by ChrisDolan (2855)

    Interesting, I had not heard of ShipIt. I'll look at it.
    
    I looked at your changelog [cpan.org] and I have to say in all modesty, I like my own syntax a lot more than yours. I think my choice to make version numbers the key of the hash increases the readability of the file dramatically.
    
    I'm definitely in favor of standardization, but if it's going to be YAML (instead of more interoperable XML) then it had better emphasize the YAML advantage of human-readability.
    • Re: (Score:1)

      by hanekomu (8123)

      In an earlier version, I had the version numbers as the keys. Didn't work out very well - there were complaints of it all being too indented. Also, now I can verify the validity of the Changes file with a Kwalify syntax.

      But it doesn't matter - you can just write a new parser and a new formatter for Module::Changes. I'd have to change the bin/changes program to take args for different parser and formatters (maybe get them from some ~/.changesrc), but that's easy.
• Simple == Good :-D (Score:1)

  by sjn (3626)

  I like what you've done with the Changelog files you linked to. They're easy on the eye, allow for the necessary information, and preserve scannability.
  
  Well done! :-D
  
  Now, which keys should be standardized? Could some of the keys be simpler/made more obvious? Is it possible to link the commit log facilities in SVN (or such) to this?
  
  I love what you've done here! ^^