I tend towards the second and third options. Each file has its own version number which gets bumped, e.g., from 1.0.0 to 1.0.1 each time it's modified. Once I'm ready to issue the next release, I sync all version numbers to 1.1.0 and go from there for further changes.

Aside from this generally making sense to me, it makes it easy when a client reports a problem that I thought I fixed last week - "What version of Foo::Bar.pm are you using?" "1.0.1" "Still? I sent you 1.0.4 last night... Here's a fresh copy of it." - without having to start diffing his version of the code against mine or hoping I notice that it's a stale version before spending too much time trying to isolate the "new" bug.

In reply to Re: One global $VERSION number in modules by dsheroh
in thread $VERSION in modules with multiple packages by lima1

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.