-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time for a new release #7
Comments
@racke @ikedas @dverdin I think that now we have have the comaintainership on PAUSE, it’s time for a new release (2.6.20). Is that OK for you ? Once I got at lease 2 "Go", I’ll do all the stuff listed in this issue. NB: I merged #9, which adds the github url for issue tracking and #4 (code tidying). #4 was first associated to the 2.6.21 milestone but it seemed ok to me to merge it now. |
@ldidry yes please go ahead, that's about time for the release 😬 |
@ldidry, it's OK for me. Thanks for your work! |
@ldidry Please let us know when the module is released to CPAN. |
I uploaded it but it seems there is a problem: Click to see the error message from PAUSE
I then checked that I have the right permissions on MHonArc on PAUSE, and it seems OK. I asked for a re-indexation. Now, we have to wait. |
Indeed weird .... |
Same error after asking for re-indexing 🤔 |
Contact PAUSE admins? |
Weird. I confirmed we are co-maint of MHonArc.
In this commit, changes such as + use MHonArc;
+ our $VERSION = $MHonArc::VERSION; seem not working as expected. I guess Perl code migiht not be executed to detect version number during indexing by PAUSE: Instead, a literal version string should be written, like + our $VERSION = '2.6.20'; |
I see that the name of the primary maintainer is missing in PAUSE’s message ( For the I’ll revert the changes relative to the |
Wrong: I’ll contact the PAUSE admins before doing anything. |
I decided to revert my changes about the |
It is recommended that all library files in the module have our $VERSION = '2.6.20'; to each |
Ok. Pretty annoying when changing the version, but ok. |
That's a Perl oneliner .... |
Yes, sure, but you need to think to do it when releasing a new version. |
That’s kind of weird that no version was in the modules before and pause indexing worked 🤔 Anyway, I asked for deletion of my faulty tarball, I need to wait until 18 september (friday) before being able to push my new version (I don’t want to increase the version number on each try). I post that here as a reminder how to change version number everywhere:
|
I finally created a 2.6.22 version: even if the previous 2.6.21 files were deleted on PAUSE, I got a conflict when trying to upload a 2.6.21 package. |
You may try with e.g. 2.6.21_1, then if things will go fine, you may upload 2.6.22. suffix _1, _2,... means the unstable release after the last stable release (eg. 2.6.21_1 means such as 2.6.22beta). |
Too late, it is already on CPAN 😁 |
I just received¹ a mail from Neil Bowers, it’s a pb on PAUSE because MHonArc didn’t have a MHonArc.pm. TL;DR: he will try to fix the pb and trigger a reindexing of my latest upload. ¹ and sympa-developpers ML was CC |
OK please let's add that module for the next release. |
develop
intomaster
perl Makefile.PL; make; make tardist
) and upload it to PAUSE¹master
intodevelop
develop
if needed¹ Need for the community to have co-maintainership of MHonArc on PAUSE
The text was updated successfully, but these errors were encountered: