The principles of CM merely require that CIs (configuration items) have a means of identification such that different CIs and different compositions/versions of those CIs be readily distinguished.

In the case of perl, the CIs are modules whose name distinguishes them apart from other modules and $VERSION distinguishes between the versions of a module.

Whilst not mandated, it is conventional that the versioning scheme readily supports the determination of the temporal ordering of the individual CI versions. To this end, as has been stated elsewhere, the versioning scheme of choice should follow the above whilst allowing for the nuances of perl in it's interpretation of the version identifier.

FWIW, my preference is to utilise an ISO 8601 style time/datestamp with all separators removed thus removing any mis-interpretation (pun intended) by perl since all version ids are merely, albeit lengthy, integers whose value specifies when the module was checked in i.e. became repeatable. The use of ISO 8601 c/w epoch timestamping, future proofs the versioning against the epoch roll-over.

Just my 10 penn'orth

A user level that continues to overstate my experience :-))

In reply to Re^3: Module version numbers best practice (meaning--) by Bloodnok
in thread Module version numbers best practice by hippo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.