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.
  • You say:

    Number of stable Rakudo (Perl 6 on Parrot) releases since the Perl 6 project began in summer 2000: 17.

    Patrick's latest release announcement [perl.org] says:

    On behalf of the Rakudo development team, I'm pleased to announce the May 2009 development release of Rakudo Perl #17 "Stockholm".

    (and the previous 3 announcements are similar - I didn't check further than that.

    • If I recall correctly, the intent behind the wording of Rakudo's release announcements -- as well as its version numbers -- is to reduce the possibility of people expecting that any monthly release represents the whole of Perl 6.0.

      I hate the linguistic games around "stable" and "maintenance" and "development" almost as much as I hate the magical thinking around version numbers.

      With that said, I use the word "stable" to mean "passes tests on supported platforms" and "performs as intended". It's not the fina

      • Rakudo uses the phrase "development release" primarily as a way of indicating "No, we aren't claiming that it's Christmas yet." More formally, it's an explicit recognition that there are significant portions of the Perl 6 specification that Rakudo doesn't support yet.

        We don't (yet?) make any official claims about Rakudo's suitability for given purposes. Do I think Rakudo is ready today for a wide variety of general-purpose applications? No. Can I conceive that Rakudo today could be usable for more than just exploration of Perl 6? Yes. Do I expect to see an increasing population of Rakudo users (as opposed to explorers and developers) in the relatively near future? Definitely.

        In general, with each Rakudo release we aim for the following:

        1. Anything that is in the current Perl 6 specification and that worked in the previous release continues to work in the new release.

        2. At least some new features or capabilities have been added over the previous release.

        3. At least some bugs in the previous release have been addressed in the new release.

        4. The overall build/install/usage/documentation infrastructure for Rakudo Perl has been improved.

        Over the next few months I expect to have discussions and plans about when we'll switch from "development release" to using some other term that indicates that we think Rakudo has progressed beyond the "Innovators and Explorers" stage to being usable by Early Adopters [1]. And I think that switch will likely occur within the next 3-9 months (the imprecision here is due to uncertainty about what we need to achieve before making that switch, the stability of the Perl 6 specification itself, and our overall rate of development progress).

        Pm

        [1] http://en.wikipedia.org/wiki/Technology_adoption_lifecycle [wikipedia.org]