Charlie, A question. So, the stdlib should be updated to the latest official 1.8.6 version? That would be great! And we should probably also change the RUBY_VERSION number from 1.8.5 to 1.8.6.
Currently, in compatibility tests/fixes, we target the latest MRI 1.8.6 as the reference implementation, and there were a couple of cases when we claim 1.8.5 but actually behave as 1.8.6. Thanks, --Vladimir On Dec 26, 2007 10:13 PM, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > I think perhaps we should cut it off finally and say that feature > changes will be frozen for the 1st, with an RC immediately after. > Basically all milestones we wanted to reach for 1.1 have been met. All > that should be left for the 1.1 release is bug and compatibility fixes > (including memory improvements or performance improvements if they > constitute bugs themselves). > > So I propose: > > - Jan 1st is feature-freeze. No new features or major reworks after the 1st. > - Some time later next week we'll put out 1.1 RC1 > - Only compatibility/bug fixes should go in after that > > So if you have any major perf or library rework you want to do, we > should have it in by the 1st. We should also try to have updated > versions of Ruby stdlib and all dependency JAR files before then as well. > > And I think we should target late January for 1.1 final. > > Agreed? > > - Charlie > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
