[#11439] comments needed for Random class — "NAKAMURA, Hiroshi" <nakahiro@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2007/06/12

[#11450] Re: new method dispatch rule (matz' proposal) — David Flanagan <david@...>

This is a late response to the very long thread that started back in

17 messages 2007/06/13

[#11482] Ruby Changes Its Mind About Non-Word Characters — James Edward Gray II <james@...>

Does this look like a bug to anyone else?

10 messages 2007/06/16

[#11505] Question about the patchlevel release cycle — Sylvain Joyeux <sylvain.joyeux@...4x.org>

1.8.6 thread support was broken in bad ways. It stayed for three months

20 messages 2007/06/20
[#11512] Re: Question about the patchlevel release cycle — Urabe Shyouhei <shyouhei@...> 2007/06/20

Hi, I'm the 1.8.6 branch manager.

[#11543] Re: Apple reportedly to ship with ruby 1.8.6-p36 unless informed what to patch — James Edward Gray II <james@...>

On Jun 27, 2007, at 4:47 PM, Bill Kelly wrote:

10 messages 2007/06/27

Re: Question about the patchlevel release cycle

From: Ryan Davis <ryand-ruby@...>
Date: 2007-06-20 06:30:11 UTC
List: ruby-core #11506
On Jun 19, 2007, at 23:11 , Sylvain Joyeux wrote:

> 1.8.6 thread support was broken in bad ways. It stayed for three  
> months
>
> 1.8.6-p36 is broken w.r.t. compilation of extensions and has a  
> thread bug.
> The bug is much minor than in 1.8.6, but it is nonetheless a bug in a
> very "core" part of the standard library.
>
> Wouldn't it be possible to have "hotfixes" (i.e.: quick patchlevel
> releases) when this kind of bugs happen ?

could you refer to bug #s?



In This Thread