I had been wanting to back-port a PostgreSQL auto-reconnect fix. Since that's not a security issue though, I guess it's not appropriate for Rails 3.1. I have written a trivial initializer for my employer that patches the problem in 3.1, so I'll just ask permission to publish that as a Gist for anyone who needs it.
I'll probably still go ahead and fix the build if no one beats (or has beaten) me to it. On Friday, September 14, 2012 6:58:48 AM UTC-7, Rafael Mendonça França wrote: > > Security patch should not be sent in the issues tracker. Read this page if > you think your bug is a security one http://rubyonrails.org/security > > Rafael Mendonça França > http://twitter.com/rafaelfranca > https://github.com/rafaelfranca > > > > On Fri, Sep 14, 2012 at 6:11 AM, Jon Leighton > <[email protected]<javascript:> > > wrote: > >> On 14/09/12 06:07, Steve Jorgensen wrote: >> > Oh -- good to know. If I submit a trivial non-security pull request, is >> > it likely to be accepted? >> >> If you submit a PR against 3.1 with the sole purpose of fixing broken >> tests, I'll happily merge. We'll need those tests to work if/when there >> are future security patches to apply anyway. >> >> -- >> http://jonathanleighton.com/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-core?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/BgCIYJktpiAJ. 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/rubyonrails-core?hl=en.
