[#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: "Michal Suchanek" <hramrach@...>
Date: 2007-06-20 21:25:13 UTC
List: ruby-core #11521
On 20/06/07, Alexey Verkhovsky <alexey.verkhovsky@gmail.com> wrote:
> On 6/20/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
> > 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.
>
> As a downstream packager of sorts (http://rubyworks.thoughtworks.com),
> I would be delighted, not annoyed, to receive a message every couple
> of days (historical rate of patchlevel tags for 1.8.6) along the lines
> of "hi, I've just tagged patchlevel X, it fixes bugs Y and Z".
>
> I realize that the same information could be obtained by watching the
> 1_8_6 branch on Subversion, but that's extra digging for the knowledge
> you have in your head when you tag a patchlevel.
>
The commit messages should include that so it's only a matter of
sending the commit messages to some sort of mailing list to which
people could subscribe.
You should be able to get the equivalent with a web scraping tool as
long as the repository is web-accessible. Or a script that reads the
svn, iirc there are even ruby bindings.

Thanks

Michal

In This Thread