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.

  • Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we continue to recommend that people wanting to use or work with Rakudo obtain the latest source directly from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo [rakudo.org] .

    This release announcement reads to me as...

    "We've released the new version of Rakudo. Don't use it. If you're sophisticated enough to have and use git, pull from version control, set up

    • If people are interested in Perl 6, is it really SO bad that they are running 1-4 weeks behind the bleading edge?

      No, but they're probably missing out if they're a week behind the bleeding edge. The pace of development can be astounding. Ask anyone who's used it this year.

      Why bother doing releases at all?

      So that code regularly reaches a wider audience of users and potential testers and contributors.

      So that people don't have to track trunk.

      So that people have a regular stable distribution of Rakudo at

      • In addition to all of the reasons chromatic gives, I'd add:

        * We'd like to avoid getting bug reports and questions about things that were fixed 1-4 weeks prior.

        * Application developers often like to target releases instead of trunk for their distributions.

        * Many people still believe the myth that Perl 6 is vaporware and will never exist/be finished/be released/etc. The best response to that myth that I can offer is a steady stream of regular releases showing measurable progress towards the goal.

        ----

        With all of the above said, we are nearing the point where I think it's reasonable for people to work from releases instead of trunk, and the release announcement text will likely change soon to reflect that. However, as of the May release we weren't there yet, and as far as I'm concerned we aren't there until we have a truly installable Rakudo. As I noted in another thread [1] Parrot really didn't make that feasible for us until just this week.

        [1] http://use.perl.org/comments.pl?sid=43077&cid=68841 [perl.org]

        Alias, I know you got a bit burned last Fall while trying to create an installable version of Parrot/Rakudo last, and all I can offer is that I've been harping about Parrot's installation issues since long before that. It's only within the past couple of months that we've seen real progress on that front.

        ----

        Ultimately I think the primary reason for regular releases is because it forces us to regularly evaluate our progress, so that we can recognize our successes and bring attention to our shortcomings. Or, in agile development terms, we would say that the regular releases set the rhythm of our development, and short release cycles are conducive to better planning and execution.

        Or in the long tradition of open source: "Release early, release often".

        Pm