Parrot is a foundering project on top of a wonderful vision.

Will Coleda will at
Thu Sep 8 00:10:13 UTC 2011

On Wed, Sep 7, 2011 at 4:52 PM, Moritz Lenz <moritz at> wrote:
> On 09/07/2011 09:46 PM, Jonathan "Duke" Leto wrote:
>> I talked to moritz++ on IRC [0] and he commented that Parrot stable releases
>> don't really feel like stable releases, because Rakudo has been bit by huge
>> performance regressions in stable releases.
> That wasn't quite my reasoning. My argument was more that stable
> releases don't feel better in any way, and that performance regression
> was just an example.
>> Even though we are more careful about doing big merges before stable releases,
>> they really aren't much more stable than dev releases. We are lying to our
>> users. We should stop that. I propose that stable releases be put on hiatus,
>> until there comes a time when we want to reinstate stable releases.
> They do serve a purpose though: most distributions don't want to track
> monthly releases, so we need to present a recommendation which version
> to ship. If we abolish "stable" releases, we should have at least
> "recommended" releases, even if there's no real reason to recommend them
> over other releases.

We have tried to emphasize "supported" rather than "stable", and I
think the every 3 month schedule there works in light of

Even duke called them stable in his email, though, so this distinction
probably needs more marketing.

>> That being said, the way we store structured deprecation data in
>> api.yaml [4] will
>> become even more vital.
> I'm curious, is there a plan how exactly a HLL dev could profit from
> that data? (sorry for getting a bit off-topic here)
>> Parrot needs to assume that Rakudo will port themselves to another VM or write
>> their own.
> Just for clarity, Rakudo doesn't want to move away from Parrot, but
> cater to multiple backends, Parrot being one of them. (I think most
> Parrot developers are well aware of that, but it doesn't hurt to repeat it.)
> Cheers,
> Moritz
> _______________________________________________

Will "Coke" Coleda

More information about the parrot-dev mailing list