- Rakudo Perl Roadmap
- Background
- Q: How to drive/sustain Rakudo development?
- A: Perl 6 Applications
- November, Druid, Proto, ...
- find bugs
- highlight needed features
- highlight Perl 6 spec issues
- but
- ☹
- Authors won't start writing applications until Rakudo is "complete"
- Authors won't start writing applications until Perl 6 is "complete"
- ☺ Answer ☺
- Avoid the concept of
"finished" - What Rakudo will do
(as a project) - We will make
- When we will do it
- Spring 2010
(April 2010) - What will it have?
- What will it have?
What won't it have? - Rakudo BOF, 2009-08-04
- What will it be called?
- Rakudo 1.0 ✗
- ...we also want to re-think
the meaning of "Perl 6 release"
So... - Rakudo X
- Rakudo "whatever"
- Rakudo *
- Rakudo *
"Rakudo Star" - (working name)
- Roadmap
- Compiler Roadmap
- new tools → new processes
- new tools → new processes
new tools → paradigm shift - We have "Language Synopses"
- We need "Community Synopses"
- Conclusion
- Our roadmap to Spring 2010
- Our roadmap to Spring 2010
- GONG