Re^4: CPAN Testers

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?

Comment on Re^4: CPAN Testers Download Code

Replies are listed 'Best First'.
Re^5: CPAN Testers by hippo (Archbishop) on Jun 01, 2023 at 09:41 UTC
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: 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. 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. 🦛	[reply]

Replies are listed 'Best First'.

Re^5: CPAN Testers
by hippo (Archbishop) on Jun 01, 2023 at 09:41 UTC

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:

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.
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.

🦛

[reply]