Hi,
I don't really care what we choose to name the next versions, so I'll
talk about them as 1.1.2, 1.2 and 2.0 respectively. It's possible the
1.2 and 2.0 is the same.
I would like to get the discussion going about what we should aim for in
the future. I'm going to collect the goals I remember, and divide them
into near term and long term. My goal is for us to actually have a real
road map we can follow.
1.1.2: (3-5 weeks from now?)
- general bug fixes
- serial numbers for classes or method named, used for flushing caches
- respond_to? call site (based on above)
1.2: (July?)
- greatly improved Rails performance
- 1.8.7 compatibility
- Rubinius simplified support
- AOT compiler ready enough to actually be usable, including tool support
- VM API implementation
2.0: (Fall?)
- Full 1.9 compatibility
- Full Rubinius support
- Java integration totally rewritten
- Light weights (not only in JI)?
It feels like it would be really nice to have a real timeline for
features like this.
Cheers
--
Ola Bini (http://ola-bini.blogspot.com)
JRuby Core Developer
Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
Practical JRuby on Rails (http://apress.com/book/view/9781590598818)
"Yields falsehood when quined" yields falsehood when quined.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
