Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This is a very good idea, but mostly because a standardised changelog format gives us options like automatic pre-release checks of the file ("Have I updated the Changes.yml file before uploading the package to CPAN?") or making new Kwalitee tests for CPAN-friendly packages. :)

    Oh, and the syntax can be "fixed" by adding a ":" after the version number (see v0.0.1 in the example).

    - v0.0.1:
      release_date: 2007-02-15
      changes:
        - initial release

    • Oh, and the syntax can be "fixed" by adding a ":" after the version number (see v0.0.1 in the example).

      No, fix it right:

      - version: v0.0.1
        release_date: 2007-02-15
        changes:
          - initial release


      And Viola! We have v0.01 of our spec! :-)
      I like YAML for its readability due to its lack of sigils (unlike JSON). And for simple YAML there is YAML::Tiny which can handle those basic structures, namely a list of hashes., just fine...