[#6864] ruby 1.8.4 rc breaks alias_method/rails in bad ways — "Ara.T.Howard" <ara.t.howard@...>

20 messages 2005/12/09
[#6870] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2005/12/12

Ara.T.Howard wrote:

[#6872] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, [ISO-8859-15] Florian Growrote:

[#6873] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — James Edward Gray II <james@...> 2005/12/12

On Dec 12, 2005, at 1:19 PM, ara.t.howard@noaa.gov wrote:

[#6874] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, James Edward Gray II wrote:

[#6891] Time.utc! and Time.localtime! — Daniel Hobe <hobe@...>

Writing a script yesterday I found out, much to my surprise, that the

16 messages 2005/12/14

[#6918] change to yaml in 1.8.4 — ara.t.howard@...

14 messages 2005/12/16

[#6934] 1.8.x, YAML, and release management — Ryan Davis <ryand-ruby@...>

I'm concerned that 1.8.3's acceptance of non-backwards-compatible

28 messages 2005/12/18

[#6996] Problems building 1.8.4 with VS8 C++ Express Edition (cl 14.00) — Austin Ziegler <halostatue@...>

Visual Studio C++ 2005 Express Edition (VS 8.0)

20 messages 2005/12/27

Re: 1.8.x, YAML, and release management

From: why the lucky stiff <ruby-core@...>
Date: 2005-12-19 07:26:24 UTC
List: ruby-core #6951
Ryan Davis (ryand-ruby@zenspider.com) wrote:
> If this is the general consensus, I'd like to see the format change  
> in YAML be rolled back for 1.8.4 or for a soon-to-follow 1.8.5 to put  
> 1.8 back on track. If it is not the general consensus, I'd like to  
> put this on the table for discussion. 

Sorry about the silence, it was not intentional.  My time online has
been limited lately and I haven't been checking ruby-core.

We are beyond code freeze but Matz has said he will allow patches for
serious bugs.  If he's okay with it, it's literally a single byte patch.

I have started a test harness which will let me test backwards
compatibility between stable Ruby and my development Ruby, but I haven't
made a whole lot of progress on it in the last many weeks.  I know the
YAML module still needs much help overall and I'm very glad for the
refactoring and testing that matz, nobu, ocean, guy, akr and many others
have given.  My aging C skills wane.

Kaput,

_why

In This Thread