From: Loren Segal Date: 2011-01-25T05:26:55+09:00 Subject: [ruby-core:34840] Re: [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8? On 1/24/2011 11:19 AM, Zeno Davatz wrote: > Ok, the dbi gem does have some hickups to solve in Ruby 1.9.2 > Specially for point 2. we do not yet know why this works in Ruby 1.9.1 and needed a change for Ruby 1.9.2. 1.9.1 was the first release in the "1.9" series. It was ultimately not meant to be a stable branch and not meant to be used in production code. This is why Rails does not [officially] support 1.9.1. You should learn lessons from other projects and do the same. You shouldn't be discussing 1.9.1 at all. > So maybe this should be considered for Ruby 1.8.8 if that should be a bridge to Ruby 1.9.2. What are you asking to be considered, exactly? It's not ruby-core's responsibility to fix third-party gems. If gem X doesn't work for you, report the bug with the gem's authors and have it fixed to work in 1.9.2. Secondly, it's been nearly 100 emails and you've yet to explain how a 1.8.8 will bridge to 1.9.2 any differently than 1.8.6 or 1.8.7. Hash iteration will still be what it is in 1.9.2, regardless of what it changes to in 1.8.8. So here are the two possible outcomes of a new minor in the 1.8 series: 1. 1.8.8 doesn't change hash iteration and your dbi gem still works-- but you still have to find a new gem to complete the upgrade to 1.9.2 2. 1.8.8 DOES change hash iteration and the dbi gem breaks. You still have to find a new gem, this time for 1.8.8. In either case you have to find a new gem. So how about you short circuit the paths and just go find a new working gem already? A few alternatives were proposed in this thread, and your application could have been up and running in 1.9.2 by now. - Loren