in reply to Re^2: What basic things should I know about versioning modules?
in thread What basic things should I know about versioning modules?

Also, when is the thumb rule for creating new versions? If I fix a typo in a comment, should I increment the version number? I'm guessing no. But when should I?

You should definitely increment the version number on every release, as many things will depend on that (CPAN, users of your module that require a specific version, and the general confusion that comes from having two different releases with no good way of keeping them apart). Then, consider whether you need to make a release if all you did is change a code comment.

Things are of course different for modules that are just for internal consumption, in that case the only person the version numbers will have an importance for is you, and you can do things as you like. But since keeping good version numbering is important for any code that goes beyond yourself, it's a good habit to get into.

  • Comment on Re^3: What basic things should I know about versioning modules?

Replies are listed 'Best First'.
Re^4: What basic things should I know about versioning modules?
by nysus (Parson) on Feb 23, 2017 at 13:05 UTC

    Yeah, right now I'm just writing modules for myself. But I want to learn good habits in case I ever go "big time" and release a module for CPAN. It's kind of a little dream of mine. :)

    $PM = "Perl Monk's";
    $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
    $nysus = $PM . ' ' . $MCF;
    Click here if you love Perl Monks