From: Yukihiro Matsumoto Date: 2009-02-13T17:10:20+09:00 Subject: Re: If you are unhappy with the direction of Ruby 1.8.7+, respond Hi, In message "Re: If you are unhappy with the direction of Ruby 1.8.7+, respond" on Fri, 13 Feb 2009 16:41:25 +0900, Michal Suchanek writes: |I'm sorry if I personally added to this kind of view. Unlike earlier |releases I had some minor problem with code not running after upgrade |to 1.8.7, and it seemed many other people have similar experience. |While acceptable for your own code it is not good for code you |distribute to somebody else. | I expect you to be more concrete and specific about minor problems. As far as I know: * Rails had problem from method name conflict. This was unfortunate, caused by Rails' fragile monkey patching and our bad for lack of thorough Rails test before 1.8.7. It is fixed now. * erb also had a bug in 1.8.7 initial release. It is fixed now. * two other problems are reported (SWIG and hash order), and as far as I understand, they both contain bugs that haven't disclosed for 1.8.6 by accident. I consider them minor and not being worse than previous releases. Most of them are addressed already. Am I missing something? |Back then nobody stepped up and said that if code working on 1.8.6 |broke it is a bug so I just left it at that - the compatibility seemed |to be not so great. If compatibility of 1.8.7 is really "not so great": * if it is fixable, we can fix. * if it is minor, we can upgrade 1.8.7 (or later) whenever we want, as we did in the past. * if upgrading is not affordable for enterprisey people (yes, I understand them; upgrading is costly even when incompatibility is minor), they can keep using 1.8.6, which is maintained right now. As EngineYard raised their hands, the maintenance of 1.8.6 will be kept, even after 1.8.8. If more evidence of great incompatibility is not shown, I will consider it FUD, or FUD-like at most, even though I see no bad intention from anyone. matz.