comment on

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.

In reply to Re^3: Review: CGI::Prototype by perrin
in thread Review: CGI::Prototype by dragonchild

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks