On Tue, Apr 22, 2008 at 7:51 AM, Ola Bini <[EMAIL PROTECTED]> wrote: > 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)
I would like to keep putting out 1.1.x until we encounter something which changes existing semantics. I don't consider 1.8.7 as a big change. All the stuff in 1.2 can be in point releases of 1.1.x. Actually additions to 2.0 (rubinius/1.9) can also be done during point releases of 1.1. The reason to make a major release will be when we tackle and reboot Java Integration. So I think that is a driving force for 2.0 (of whatever we call it). Timelines are a good question, but I would like to keep us on trunk as long as possible to minimize supporting multiple branches. I see most of the summer being point releases (3-4 week releases). -Tom > > 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 -- Blog: http://www.bloglines.com/blog/ThomasEEnebo Email: [EMAIL PROTECTED] , [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
