So, unless you're intentionally denoting that your module is 'pre-release', it might be best to start off at 1.0.0.
It's an interesting thought. On one hand, I can see how it might avoid a lot of needless hand wringing. Plenty of effort is spent thinking and talking about when 1.0 is going to be released. I can understand the argument that this should be headed off at the pass by just starting at 1.0 from the beginning. On the other hand, I'm not sure how much value people really put into a simple version number. There are so many different schemes that have such different amounts of value attached to them, I cannot imagine any but the most naive user attributing very much importance to them.
Sure, people talk about it a lot, but do experienced admins or programmers really make decisions about what to used based on a number? I think (hope?) they go more on their peers' opinions, and the gut feeling they get when doing basic research on the project. Granted, examining the version numbers may be a small portion of that research. But I know I certainly spend more time browsing the documentation, looking for functionality, signs of maturity, and basic traces of sanity.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||