Changes for version v0.8.1_02-TRIAL - 2015-10-02 (TRIAL RELEASE)
- `example.t` test is too sensitive: it requires the manifest samples saved in `ex/` subdirectory, are generated with current version of the plugin, otherwise the test fails doe to different files. The test fixed. Now change in the plugin version does not cause the test failure.
- Bug found: when the plugin adds itself to the list of metainfo providers, it adds plugin moniker (but should add plugin name). Fixed.
- Problem found: Dist::Zilla plugins used in tests are not included into `Meta.JSON` as test requirements. Fixed.
Changes for version v0.8.1_01-TRIAL - 2015-10-01 (TRIAL RELEASE)
- In documentation, code and comments the terms "plugin name" and "plugin moniker" used more accurately. To the manual added a section explaining these terms.
- Options `source_providers` and `metainfo_providers` changed a bit. Now they split their values at whitespace (`\s+`) not on plain space.
- Options `source_provider` and `metainfo_provider` introduced. Each option treats its value as *one* plugin name. It allows to operate with plugin names containing spaces.
- Option `show_mungers` introduced. By default mungers are not shown because this information is unreliable. See <https://github.com/rjbs/Dist-Zilla/issues/495>
- Testing improved. Added a test routine (it is used in every test) to read generated `MANIFEST` with `ExtUtils::Manifest::maniread` and verify read content. That actually means my manifest is tested on compatibility with `MakeMaker`.
- If filename includes hash character, filename in manifest will be written as single-quoted string. It prevents interpreting a file which name starts with hash as a comment.
- From user point of view, this version is almost compatible with the previous (except very minor change in `source_providers` and `metainfo_providers`). However, in class interface there are incompatible changes. Some methods are renamed, some changed, so subclasses or other clients should be modified to work with the new version. (Frankly, I do not think someone uses it programmatically.)
Documentation
Manifest::Write plugin user manual
Modules
Have annotated distribution manifest