We are planning a 1.5.2 for primarily three issues which are affecting production servers without a reasonable workaround. In general, anything which has a workaround or was not a serious regression we hold off until the next 1.x series. For 1.5.2 the only issues we are considering so far are:
# JRUBY-4767 2010-04-30T11-38 Yesterday 4:40 PM JRuby and open-uri File handle issue # Bug JRUBY-4981 2010-07-30T12-51 Yesterday 4:39 PM Anonymous classes are piling up and filling up PErmGen, eventually causing a crash # Bug JRUBY-4841 2010-06-02T13-27 Yesterday 4:39 PM CLONE -Memory Leak when extending Java class with additional Ruby instance variable We will talk about whether to put in JRUBY-4937 for inclusion, but we want to be very conservative on what goes into 1.5.x so that people using 1.5.1 has an easier time moving their production systems to it. The more we put in the harder that decision becomes. -Tom On Wed, Aug 4, 2010 at 1:42 AM, David Kellum <de...@gravitext.com> wrote: > Hi, > > I saw you now have plans for a JRuby 1.5.2 release ahead of 1.6.0. I think > that's a great move BTW, toward getting fixes out sooner. What's the > decision process for what's going to make 1.5.2? > > I was hoping JRUBY-4937 (master: a7f621..009d5e) might make it, as it fixes > a old regression in a safe way (and happens to be biting me.) > > Thanks, > David > > > -- blog: http://blog.enebo.com twitter: tom_enebo mail: tom.en...@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
