- New upstream release 0.21:
Spec Changes:
- Bump version to 0.02
- Added "unknown/dev" release date options (CPAN RT #67705)
- Added optional release note (CPAN RT #69321)
- Added another preamble example
- Added a note about line length
Code Changes:
- Require Test::More 0.96 (RT #84994)
- Added --check and --help flags to tidy_changelog script
- Properly parse multi-line preamble
- Test::CPAN::Changes now warns about parsed dates not in spec-compliant form
- Handle unknown/dev release dates and release note from new spec
- BR: perl(Pod::Usage)
- New upstream release 0.20:
- 'delete_empty_groups' shouldn't erronously delete default group
- Add tidy_changelog utility script
- Minor pod fix
- Bump Test::More version requirement to 0.96 (CPAN RT#84994)
- New upstream release 0.19:
- Test::CPAN::Changes now accepts version entries ending in '-TRIAL'
(CPAN RT#76882)
- releases() in CPAN::Changes also accepts entries ending in '-TRIAL'
- Don't need to remove empty directories from buildroot
- Drop %defattr, redundant since rpm 4.4
- New upstream release 0.18:
- Expand changes_file_ok() to accept arguments so that a specific version may
be checked
- Add $VERSION to Test::CPAN::Changes so it plays nice with the toolchain
e.g. Module::Install::AuthorRequires
- New upstream release 0.17:
- Eliminate extra whitespace when release data is not defined (CPAN RT#67441)
- Require version.pm 0.79, which introduced the $LAX regexp (CPAN RT#67613)
- Add the option to sort groups
It is standard practice to include a Changes file in your distribution. The
purpose of the Changes file is to help a user figure out what has changed
since the last release.
People have devised many ways to write the Changes file. A preliminary
specification has been created (CPAN::Changes::Spec) to encourage module
authors to write clear and concise Changes.
This module will help users programmatically read and write Changes files
that conform to the specification.
