I still widely deploy to ruby 1.8.7, namely because of legacy code-base. I've started trying to convert legacy code to 1.9.2, but definitely have a lot of places that break on 1.9.2 at the moment (not just with Sequel, but project-wide). For me, this is about 100 micro-projects and about 10 major projects -- perhaps around 150k lines of code.
Michael On Sat, Jul 9, 2011 at 7:55 PM, Jeremy Evans <[email protected]> wrote: > Sequel is still fully supported and tested with Ruby 1.8.6. However, > there are a couple of places where Sequel has to go out of its way to > maintain backwards compatibility. I don't have a problem with that if > there are still people using Ruby 1.8.6, but if nobody is, that's just > wasted code. Anyway, if you have an opinion one way or another, > please speak up. > > Jeremy > > -- > You received this message because you are subscribed to the Google Groups > "sequel-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sequel-talk?hl=en. > > -- http://codeconnoisseur.org -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
