Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I prefer to look at the Changes log, rather than the version. A decent Changes log will tell you how the project has evolved and give you an indication of its stability. I've dismissed several modules based on their Changes logs. Small versions don't bother me so much, if the author has simply incremented by 0.01 each time they released to CPAN. Even jumps in versions don't annoy me, as long as there's a clear, consistent reason behind it (for example API changes). I'm particularly annoyed, however, when v

    • I think you missed the point. The programmers aren't complaining.

      when you have people having to get modules approved for use, there are people that care about versions.

      It is the $boss, who hasn't a clue about Perl (he would write it as PERL), who is looking at version numbers.

      • by Alias (5735) on 2006.05.23 20:28 (#47816) Homepage Journal
        Indeed.

        And zero-versions can make $bosses nervous.

        Of course, you have to balance that against the problem of going to 1 too early and scaring the developers.

        If 1.0 isn't stable, and lets assume they are fairly clueless just-getting-stuff-done Perl-as-a-better-sh etc types, how are they to judge when it is done?

        Looking at, for example, Module::Install, the Changes file won't help them much to know that out of all the versions, 0.61 is the first version considered "safe'ish for early adopters".

        Or look at Class::Inspector's Changes file [cpan.org]. I went to 1.0 too early on that one. Who's to know when it's "done"?

        Compare that with the Test::SubCalls Changes file [perl.org], which now has a stable version number, and for those reading the Changes file makes an obvious and definite step from 0.XX to 1.XX.

        When faced with a situation in which you have _extremely_ limited knowledge based on your ability with Perl itself, which of the two makes it appear more clearly that the module is "done" now.