in reply to Re^9: Perl Contempt in My Workplace
in thread Perl Contempt in My Workplace

I consider everything below 1.0 as experimental, whereas 0.0x as *highly* experimental. Module version above 1.0 means that author(s) have some promises to their users

Sorry, but you're mistaken. Even a quick look at CPAN shows that many stable, well-tested modules with lots of dependencies are below 1.0.

Replies are listed 'Best First'.
Re^11: Perl Contempt in My Workplace
by eyepopslikeamosquito (Archbishop) on May 06, 2021 at 11:00 UTC

    Can anyone provide a definitive reference on the meaning of version 1.0 in the Perl world, especially for CPAN modules? ... along with advice on how a CPAN module should advertise that it is stable, well-tested and not experimental.

    As indicated here I'm eager to update Writing Solid CPAN Modules with decent versioning advice but have left this in the too hard basket for far too long. :)

    I sympathise with the OP because in the mainstream software world, I've always believed that version 1.0 indicated a stable, supported, production (not development) release. For example, from SemVer:

    The simplest thing to do is start your initial development release at 0.1.0 ... If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0.

    Oh, and other cool Perl versioning references you may know of that are not mentioned here are also welcome.

[reply]
      Can anyone provide a definitive reference on the meaning of version 1.0 in the Perl world, especially for CPAN modules?

      I very much doubt you will find that because I do not think such meaning exists.

      along with advice on how a CPAN module should advertise that it is stable, well-tested and not experimental.

      That one definitely does have an answer and it is release_status => 'stable'.

      🦛

[reply]
[d/l]

      Just my two cents:

      Can anyone provide a definitive reference on the meaning of version 1.0 in the Perl world, especially for CPAN modules?

      I've always thought it was pretty arbitrary, that is, TIMTOWTDI...

      advice on how a CPAN module should advertise that it is stable, well-tested and not experimental.

      That's a good question. Personally I would make a note in the POD and/or Changelog if a version is stable - though I tend to only release decently-tested stuff anyway. If I was giving advice to someone else, what you quoted from SemVer is probably good advice. And I wrote a bit about judging the quality of a CPAN module here. (Update: hippo also makes a good point here.)

      Oh, and other cool Perl versioning references you may know of that are not mentioned here are also welcome.

      My bookmarks on versioning modules currently are: 1182640 and 11114665.

[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Meditations