- 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.
Dennis Gilmore
Marcela Mašláňová
Petr Písař
Paul Howarth
Fedora Release Engineering