Semantic versioning may cause downstream problems in Perl core distribution about podlators HOT 5 CLOSED

Thanks, in retrospect I should have realized I needed to raise this as well once I realized that all the Perl tooling wants to copy the v into the distribution name (and that appears to be the practice on CPAN as well for modules using v-strings as versions).

I'll raise this on P5P and start the yackfest. I would really like to standardize on semantic versioning for all the software I maintain, and am willing to submit PRs to Perl to fix the scripts.

from podlators.

Thanks, in retrospect I should have realized I needed to raise this as well once I realized that all the Perl tooling wants to copy the v into the distribution name (and that appears to be the practice on CPAN as well for modules using v-strings as versions.

I'll raise this on P5P and start the yackfest. I would really like to standardize on semantic versioning for all the software I maintain, and am willing to submit PRs to Perl to fix the scripts.

I just ran minicpan and can now state that there are many distros with vN.N.N version numbers in their names. But I can't recall seeing that pattern in Perl 5 core in the 12 years I've been working on it. I'm trying to think of a way to simulate the workings of those programs.

from podlators.

I don't really see this as something that has to be preemptively fixed. If there are problems with things like the sync-with-cpan or core-cpan-diff scripts, they will be trivial to fix. And that can happen after there is a release to work with.

from podlators.

Ongoing discussion in perl core: Perl/perl5#22101

from podlators.

Ongoing discussion in perl core: Perl/perl5#22101

Since I've green-lit the patch found in the core pull request cited above, this ticket is moot. Thanks.

from podlators.