I think only some one far detached from reality would expect, a Perl 5 like ecosystem ready on the day of Perl 6.0.0 release. And most people don't need many Perl 6 esoteric features either. So I guess your "a list of big ticket items remaining" hopefully won't be "a big list of ticket items remaining".
Besides I was of an opinion even after the 6.0.0 release the spec won't be complete. Spec will never be complete. Spec is a backwards compatible changing piece of document which the implementation tries to catch up with. The stable releases of the implementation are production releases.
Lastly you could just say. Esoteric features a, b, c, d are left for next 6.* releases. While release a 6.0.0 release is cut after with whatever you decide from that list earlier. The world is in no hurry to use the esoteric features anyway.
Either way, I wish you guys all the very best. And hope to soon see a closure soon on this.
> I think only some one far detached from reality would expect, a Perl 5 like ecosystem ready on the day of Perl 6.0.0 release.
I think it's still plausible that someone (it'll have to be one or more serious P5 guts hackers) will soon start implementing something like diakopter's plan for P5+XS interop. (That's the plan for having P6 code calling P5 code and back again, including XS modules on CPAN.) If that works out well, a 6.0 release could be viewed as including all of the P5 ecosystem or, conversely, as an experimental part of P5.
But perhaps I'm far detached from reality.
I certainly wouldn't expect the project to wait for such interop. If 6.0 has to ship without support for P5+XS modules, so be it.
> So I guess your "a list of big ticket items remaining" hopefully won't be "a big list of ticket items remaining".
> Besides I was of an opinion even after the 6.0.0 release the spec won't be complete.
It sounds like the plan is to mark particular bits (paragraphs?) as either 6.0 or post 6.0 and associated spectests will determine whether or not Rakudo is compliant.
> Esoteric features a, b, c, d are left for next 6.* releases.
I don't know about the esoteric aspect being the decider, but yes, I'm assuming the basic idea will be to defer as much as is reasonable.
> Either way, I wish you guys all the very best. And hope to soon see a closure soon on this.
{ "this" }
Maybe not what you're after?
Seriously, while I hope for a 6.0 spec this year I think there's about zero chance of a 6.0 Rakudo this year. And unless a few dozen more contributors turn up maybe not in 2015 either.
Besides I was of an opinion even after the 6.0.0 release the spec won't be complete. Spec will never be complete. Spec is a backwards compatible changing piece of document which the implementation tries to catch up with. The stable releases of the implementation are production releases.
Lastly you could just say. Esoteric features a, b, c, d are left for next 6.* releases. While release a 6.0.0 release is cut after with whatever you decide from that list earlier. The world is in no hurry to use the esoteric features anyway.
Either way, I wish you guys all the very best. And hope to soon see a closure soon on this.