Yep, I'm going to write a module called Module::Metadata::Changes, starting tomorrow.
I installed Module::Changes, but was so distressed by the cascade of dependencies that I resolved to try myself.
This namespace allows Module::Metadata::SomethingElse, so that's a plus.
I will adopt the nice suggestion of Marcel Grünauer as regards a typical content for a Perl module's Changes file. See his POD for details, or my POD-to-be.
And yes, I'll default to YAML, even though my reservations about YAML are even more soundly based than yours. See my FAQ-to-be for details.
I will be adding something like:
Deploy: No need
Reason: Doc or test changes only.
This allows you to Do The Right Thing with:
Reason: Development version.
After all, we don't want another Data::Dumper fiasco, do we
If use of YAML upsets you, please feel free to write a module with a name like XML2YAML2XML::Tiny, using YAML::Tiny and XML::Tiny. That'll allow us to ship all of: