Searching when the only releases of a module are dev releases

[DrHyde]

Compare: http://search.cpan.org/search?query=marpa-r3 (which returns the modules in Marpa-R3-4.001_022) and https://metacpan.org/search?q=marpa-r3 (which returns Marpa::R2::Progress from Marpa-R2-3.000000).

Right now there seem to have been three uploads of Marpa-R3, all dev releases:

• Marpa-R3-4.001_020
• Marpa-R3-4.001_021
• Marpa-R3-4.001_022

Being dev releases they're not indexed by the PAUSE. Normally we don't want dev releases to show up in search results because they're unstable and we don't want to hide stable releases. However, in this case where there are only unstable dev releases the most recent should probably show up by default.

Even if you don't return the contents of the unindexed dev release, you definitely shouldn't return the contents of any version of Marpa-R2!

[wchristian]

The label "dev_trial_release" here is inaccurate as this issue does not only affect dists that only had dev releases, but also dists that had perfectly fine, fully-fledged production releases where the last release however had an issue that dropped it out of the pause index. This isn't just "a work-in-progress is not being shown". This is "metacpan pretends an existing body of work used in production never existed".

[leonerd]

Issue still exists. My stringification has never had a real release, only devel releases. I happen to know it exists at https://metacpan.org/release/PEVANS/stringification-0.01_004 but I've never been able to see it via any search e.g. https://metacpan.org/search?size=20&q=stringification&search_type=modules