All versions of my (only) CPAN module had no known bugs when I released them (and the test code to show that the known bugs where fixed). That didn't really mean they had no bugs.
I'm not sure where you're going with that. Everything has bugs.
You point about API changes is valid, but that an API is "complete" doesn't mean it's "done". It takes a LOT of testing and tweaking to get an API "just right"
No API is ever done. They always evolve over time. If you do something drastic that breaks backwards compatibility in a big way, you can release 2.0.
The 1.0 version number is arbitrary and for marketing purposes only.
Right, which is why everyone should feel free to use it.
Programmers should know better than to trust a version number.
And yet they don't. They get scared by low version numbers. And so do their managers. That's why it matters.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.