I recently published a new module on CPAN, starting off with a vanilla version number of 1.00. Then as I was experimenting with Dist::Zilla I decided to go with a date based version scheme. Unfortunately, I messed it up. I uploaded a module with version v2022.08.30, which was acceptable to Dist::Zilla and CPAN but which I now think could create upward compatibility problems because I used the year where the Major version number should go. Now I can't use the Major version to handle interface changes, and it'll look like there's an interface change every time a new year comes along.

I want to ditch this tarball and replace it. But if I adopt a more sensible date-base versioning scheme, such as v1.22.242 (major version, year of century, day of year) then the prior version will look newer since it is v2022.

I've submitted a delete request on the tarball, but that will take a week to process. Probably by then the back-end machinery will build and test and release the thing. (It would be great if the pending delete stops that from happening -- if that is how it works, please let me know.)

Bottom line, I'm seeking is some insight into how PAUSE file deletions work, and whether there's anything else I can do to fix this mess or avoid making it worse.

In reply to Help with PAUSE mechanics - replacing a bad module by PUCKERING

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.