[#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: Urabe Shyouhei <shyouhei@...>
Date: 2007-06-20 09:11:47 UTC
List: ruby-core #11512
Hi, I'm the 1.8.6 branch manager.

Sylvain Joyeux wrote:
> Wouldn't it be possible to have "hotfixes" (i.e.: quick patchlevel 
> releases) when this kind of bugs happen ? 
>   

Well, use Subversion.

http://svn.ruby-lang.org/repos/tags
http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/tags/

This time we released particular 1.8.6-p36, but p1 to p35 also exists
there.  They were not announced because announcing every patches is way
too annoying.  Imagine more than a dozen of release announcement made in
a day or two... I bet you just ignore everything.

Anyway 3 months of release interval is not that long I feel.  Remember
there were only one chance in a year (i.e. 25th Dec.) to release a ruby
in ancient days.  Releasing too frequently is annoying as I wrote. 3
months is at once moderately long, moderately short.

In This Thread