Rakudo has no fixed schedule, so no predictions here.

I don't believe we'll see a "Rakudo 1.0" release this year, simply because too many subsystems are still missing: concurrency, IO, Unicode layers, feeds, macros, user defined operators - you name it.

That said, Rakudo is getting more usable every week, and as you can see on this chart it makes steady progress in the test suite. Some time ago I analyzed that passes 23 new tests per day, on average. Yesterday it passed 7227 tests.

Currently there are approximately 18000 tests in the test suite. At the current rate it would pass these in one year and four months.

However the current test suite doesn't cover all of Perl 6, and more tests are needed. So don't think Rakudo will be done when it passes 18k tests.

Of course this rate could change drastically if we had one or more frequent contributor. Currently most of the grunt work is done by two people, pmichaud and jnthn. Having one or two more core developers would make quite a difference.

(And do keep in mind that these are just number games: Usually the easy tests are passed first, and the hard ones take more time; so the amount of work to get new tests passing can actually increase over time).

In reply to Re: If Parrot comes, can Rakudo be far behind? by moritz
in thread If Parrot comes, can Rakudo be far behind? by xiaoyafeng

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.