Hi, I'm sure you're well aware of the email incident that GitHub experienced when upgrading to Rails 3.2.13 https://github.com/blog/1440-today-s-email-incident
A number of regressions were resolved, though some are likely to remain open to avoid symbol attacks while maintaining some semblance of backwards compatibility. There is quite a bit of discussion on issue #9813: https://github.com/rails/rails/issues/9813 I've attempted to test the issue GitHub blogged about against multiple versions of Rails using Appraisal: http://stackoverflow.com/questions/17867202/why-am-i-unable-to-reproduce-the-github-email-incident-issue And we are currently doing a query-by-query comparison of Rails 3.2.12 and Rails 3.2.14 by logging all queries generated during a test suite run: https://gist.github.com/nathany/6091516 Still we're a little uncomfortable rolling 3.2.14 into production due to the crashes we had with 3.2.13, and I personally don't feel like I fully understand all the issues. I would really like to see a formal response to the GitHub email incident, preferably on the Rails blog. What is the clobbering behaviour? What actions cause an ActiveRelation merge? What should we avoid or watch out for? Thanks, Nathan. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
