From: Louis-Philippe <default@...>
Date: 2009-02-12T02:41:02+09:00
Subject: Re: If you are unhappy with the direction of Ruby 1.8.7+, respond

--0016e6d9a15a1a10720462a8126a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

+1

1.8 should keep its final branch release as fully 1.8 compatible for
posterity.  (Keep it legacy compatible)
Ventures into the future can take place inside the Newer 1.9 and 2.0
branches without breaking what we could call "1.8 Legacy" code.

2009/2/11 James Gray <james@grayproductions.net>

> On Feb 11, 2009, at 11:10 AM, Gregory Brown wrote:
>
>  I am setting up two threads in the hopes that we can see names
>> attached to opinions about the decision to break backwards
>> compatibility between Ruby 1.8.6 and Ruby 1.8.7+
>> This one is for those who wish that Ruby 1.8 would go *back* to being
>> 1.8.6 compatible in Ruby 1.8.8.
>>
>
> I'm bothered by the new versioning scheme.
>
> The new releases involve big changes and even if they are fully backwards
> compatible about what they will run, they are still creating pretty big
> compatibility gaps.  Code using any of the new 1.8.7 features won't run on
> 1.8.6 and lower.  It sounds as if 1.8.8 intends to take this farther, so
> code written to that won't work in the different 1.8.7 branch or the earlier
> 1.8.6 and lower stuff.  Thus I feel we now have three different versions of
> Ruby 1.8 on the table (counting the not yet released 1.8.8).
>
> James Edward Gray II
>
>

--0016e6d9a15a1a10720462a8126a--