On Fri, Aug 28, 2009 at 2:21 PM, Ola Bini <ola.b...@gmail.com> wrote:

> Nick Sieger wrote:
>
>> On Thu, Aug 27, 2009 at 7:36 PM, Hirotsugu Asari<asari.r...@gmail.com>
>> wrote:
>>
>>> What is the policy about these directories, which I assume are copies of
>>> MRI's counterparts. When do they get synchronized with MRI?
>>>
>>
>> There's no strict policy, but we try to upgrade them wholesale when a
>> particular release or patchlevel of Ruby seems to stabilize. We also
>> apply critical fixes from time to time if they're security advisories
>> that look like they could affect JRuby as well.
>>
>> Also, lately we've been talking how we'd prefer not to modify them in
>> JRuby's repository because we tend to lose such modifications over
>> time.
>>
>> /Nick
>>
>>
> I've been starting to think that maybe it would be better if we could
> package our modifications as monkey patches - that way they would be totally
> separate from the files. Another alternative is to have our modifications
> represented as diffs in the repository. That might also make it easier to
> handle them.


Agree.

Although ruby critical patches are released quickly there are situations
where other non critical bugs can be solved and released first in jruby
because I think you relase new versions faster than the ruby guys so we
don't need to wait them.


>
>
> Cheers
> --
>  Ola Bini (http://olabini.com)
>  Ioke creator (http://ioke.org)
>  JRuby Core Developer (http://jruby.org)
>  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
>
>
>


-- 
David Calavera
http://www.thinkincode.net

Reply via email to