Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Re^2: CPAN Testers

by Bod (Parson)
on May 30, 2023 at 22:09 UTC ( [id://11152540]=note: print w/replies, xml ) Need Help??


in reply to Re: CPAN Testers
in thread CPAN Testers

Have you received the e-mail confirming it's been indexed by PAUSE

Yes - nearly 11 hours ago!

Google has it listed in search results and it is here

Replies are listed 'Best First'.
Re^3: CPAN Testers
by hippo (Bishop) on May 31, 2023 at 07:44 UTC

    Thanks for the link - it wasn't showing up in the main metacpan search. That is because you appear to have uploaded 2 releases within an hour of each other, one with version 0.1_1 and the other, apparently previous one, without any version info at all (and which has various other issues too). Since neither version number is a valid non-dev version it won't appear in the search results.

    Always ensure that the dist you upload has a valid version number otherwise you will encounter troubles like this.

    I would further recommend always uploading a non-dev release first. This should ensure the indexing and claim the namespace. If you start with version 0.00, it should be very clear to all users that this is the first release and unlikely to be perfect. Subsequent dev releases can address the issues there will doubtless be in this first release.

    HTH.


    🦛

      That is because you appear to have uploaded 2 releases within an hour of each other

      That is because I made a mistake creating the .tar.gz and PAUSE wasn't able to index it. So I then uploaded the correct one.

      I would further recommend always uploading a non-dev release first

      Interesting - I seem to recall reading the opposite advice but it might have just been what seemed logical!

      I need to upload a new version to cure some bugs and issues. Given where we are, would you suggest uploading v0.00 first and then v0.01_2 or going straight to v0.01_2?

        Version 0.1_1 is already extant so there is no point at all in releasing a newer version with a lower version number.

        Given where you are, I suggest:

        1. Keep releasing dev versions until you are happy with the code/tests. Your next dev version should be 0.1_2 and then 0.1_3 and so on.
        2. When you have a release you think is worthy of non-dev status, release that and bump at least the minor version. However, in your shoes I would at that point effectively start again and release 1.00.

        The more digits used in each part of the version number, the more flexibility you get to release lots of intermediate versions. Personally, I like to use double digits so my version numbers go like this:

        • 0.06 - stable release
        • 0.06_01 - dev release
        • 0.06_02 - dev release
        • 0.06_03 - dev release
        • 0.07 - stable release

        ... and so on. The numbers then are always increasing and there's plenty of scope for lots of dev releases without running out of digits. Other folks go to 3 digits in each part just like perl itself, use whichever you prefer.

        I generally agree with xdg in Version numbers should be boring which was referred to elsewhere recently.


        🦛

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11152540]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others romping around the Monastery: (7)
As of 2024-04-19 07:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found