Well, I don't think there is any hardened rule or RFC on this but there a standard as far as what your versioning is supposed to mean. That of course being the all-known major.minor.minor_minor.etc. However, I believe that the versioning is really up to the developer. It's ultimately up to you if you want to name your first version of a program as version 5. I wouldn't really recommend that but how is the end user supposed to know? I believe it really is just a way for the developer(s) to maintain the code and to be able to handle revision control a little easier. I have seen some people release their first versions as 0.x probably in anticipation of coming out soon with a better version or perhaps that is just how they want to version their software.

Some people let their revision control software do the versioning for them. eg. RCS or CVS. I like this because unless you tell the revision control to version your rev differently it just minors it up one (ie 4.1 to 4.2 etc).

In summary, I believe it is up to you. That's how I've done mine. And I do my versioning with the intent to be able to control my revs a bit better.

----------
- Jim

In reply to Re: Software (Module) Release Numbering Conventions by snafu
in thread Software (Module) Release Numbering Conventions by dpatrick

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.