Re^2: testing/release advice [was: Stopping tests]

My understanding was that we should always upload a dev release first! I thought I got that from Re: What do I use to release a module to CPAN for the first time? but rereading it, that's not where it came from...

Bod you're right, you didn't get it from the most excellent Re: What do I use to release a module to CPAN for the first time? by davido.

And you certainly didn't get it from my Writing Solid CPAN Modules ... because I'm a Dev release ignoramus :)

To remedy that I've just added some extra references to Writing Solid CPAN Modules:

perlmodstyle (perldoc) - Perl module style guide (re making a dev release: if you want to release a 'beta' or 'alpha' version of a module but don't want CPAN.pm to list it as most recent use an '_' after the regular version number followed by at least 2 digits, e.g. 1.20_01)
CPAN (perldoc) (FAQ 12) - How do I install a "DEVELOPER RELEASE" of a module? By default, CPAN will install the latest non-developer release of a module. If you want to install a dev release, you have to specify the partial path starting with the author id to the tarball you wish to install, like so: cpan> install KWILLIAMS/Module-Build-0.27_07.tar.gz
Update (thanks hippo): CPAN::Meta::Spec (perldoc) - specification for CPAN distribution metadata (for release_status, if the version field contains an underscore character, then release_status must not be "stable")

Bod: note the leading zero in Ken's Module-Build-0.27_07.tar.gz ... I think you meant to use _01, _02, ... instead of _1, _2 in your Dev releases :)

More definitive references on CPAN Dev releases welcome.

Comment on Re^2: testing/release advice [was: Stopping tests] Select or Download Code

Replies are listed 'Best First'.
Re^3: testing/release advice [was: Stopping tests] by hippo (Archbishop) on Sep 14, 2023 at 08:55 UTC
More definitive references on CPAN Dev releases welcome. Probably worth mentioning that CPAN::Meta::Spec now includes the release_status required field. The linked doc includes the proscription: If the `version` field contains an underscore character, then release_status must not be "stable." and finishes the section with: Consumers may use this field to determine how to index the distribution for CPAN or other repositories in addition to or in replacement of heuristics based on version number or file name. I see this as a belt-and-braces facility with the added bonus of being able to specify "unstable" as a value to indicate really alpha releases. 🦛	[reply] [d/l]
Re^4: testing/release advice [was: Stopping tests] by Bod (Parson) on Sep 14, 2023 at 11:46 UTC
If the version field contains an underscore character, then release_status must not be "stable." I had noticed `release_status: unstable` in the JSON file -> Re^4: testing/release advice [was: Stopping tests]	[reply] [d/l]