develooper Front page | perl.perl5.porters | Postings from February 2018

Handling of $VERSION in ExtUtils-ParseXS

Thread Next
From:
James E Keenan
Date:
February 15, 2018 15:32
Subject:
Handling of $VERSION in ExtUtils-ParseXS
Message ID:
20180215153204.6805.qmail@lists-nntp.develooper.com
ExtUtils-ParseXS is found under dist/, which means it is 
"blead-upstream."  Hence, the incrementing of $VERSION numbers is P5P's 
responsibility -- but I'm not sure of what the correct procedure is.

In this commit:
#####
commit 76eb84800b51f32ecd4ab68d15ca549f2f67721b
Author:     Father Chrysostomos <sprout@cpan.org>
AuthorDate: Sun Dec 10 16:54:44 2017 -0800
Commit:     Father Chrysostomos <sprout@cpan.org>
CommitDate: Sun Dec 10 18:19:01 2017 -0800

     Increase $ExtUtils::Typemaps::VERSION to 3.37
#####

... $VERSION was bumped *only* in 
dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps.pm.  In all the other 
dist/ExtUtils-ParseXS/lib/ExtUtils/*.pm files $VERSION remained at 3.36. 
(CPAN is still at 3.35.)

My gut feeling is that's wrong, i.e., $VERSION should have been 
incremented to 3.37 in all modules.

I ask because I'm ready to apply Pali's documentation correction, which 
necessitates a $VERSION increment in (at least) 
dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/Eval.pm.  Should I:

* bring everything up to 3.37?

* increment everything to 3.38?

Please advise.

Thank you very much.
Jim Keenan

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About