This is a huge step forward to a big release! I myself built a little app with the RC, Ruby 2.0, and deployed it to Heroku yesterday, and that whole stack works just fine. _Please_ give the RC a try, and file any issues you have on the tracker: https://github.com/rails/rails/issues?state=open There's nothing more frustrating as a maintainer than getting regression reports the day after you release when you've done tw…
692 examples, 0 failures, on both 1.9.3 and 2.0. This was the smoothest major upgrade yet, with very helpful deprecation notices. Thanks for all the hard work.
Rails 4.0: Release Candidate 1 released
31–40 of 58 posts
Re: Rails 4.0: Release Candidate 1 released
#32Re: Rails 4.0: Release Candidate 1 released
#33Earlier quoted context omitted.
The issue I keep running into when testing the RCs with larger apps is the number of gems that have strict dependencies on older versions of activesupport, etc. I am wading through my Gemfile (over 200 gems counting direct and indirect dependencies) at the moment trying to give the RC a shot, but it's going to be difficult to justify spending much more time on it, unfortunately.
Can you tell me which gems you're having problems with? I'll send a bunch of pull requests this evening.
I had a look at it and got through a bit of re-working some of the changes (indexes etc), but got pretty quickly out of my depth of understanding around the inner workings of ActiveRecord.
Re: Rails 4.0: Release Candidate 1 released
#34Would it be possible to get a TL;DR version of any decently sized changes from 4.0beta -> 4.0rc1?
Check the upgrading guide for a reasonable Tl;dr, I'm excited about strong_parameters and HTTP PATCH, personally.
Re: Rails 4.0: Release Candidate 1 released
#35This is a huge step forward to a big release! I myself built a little app with the RC, Ruby 2.0, and deployed it to Heroku yesterday, and that whole stack works just fine. _Please_ give the RC a try, and file any issues you have on the tracker: https://github.com/rails/rails/issues?state=open There's nothing more frustrating as a maintainer than getting regression reports the day after you release when you've done tw…
Re: Rails 4.0: Release Candidate 1 released
#36This is a huge step forward to a big release! I myself built a little app with the RC, Ruby 2.0, and deployed it to Heroku yesterday, and that whole stack works just fine. _Please_ give the RC a try, and file any issues you have on the tracker: https://github.com/rails/rails/issues?state=open There's nothing more frustrating as a maintainer than getting regression reports the day after you release when you've done tw…
Do you use PostgreSQL with your app on Heroku? I seem to run into problem with it: https://github.com/heroku/heroku-buildpack-ruby/pull/93
Re: Rails 4.0: Release Candidate 1 released
#37Earlier quoted context omitted.
Do you use PostgreSQL with your app on Heroku? I seem to run into problem with it: https://github.com/heroku/heroku-buildpack-ruby/pull/93
I did, yes, but I didn't have that issue.
4.0.0.beta1 works fine on Heroku but I keep running into ActiveRecord problem after upgrading to 4.0.0.rc1.
Re: Rails 4.0: Release Candidate 1 released
#38There have been enough performance and functionality related issues in 3.2.13 that I was hoping to see at 3.2.14.
Re: Rails 4.0: Release Candidate 1 released
#39Are we going to see another 3.2 release outside of security issues? There have been enough performance and functionality related issues in 3.2.13 that I was hoping to see at 3.2.14.
Tl;dr: after 4.0 is released, no. But bugfixes have been merged into 3-2-stable that there should be a 3.2.14 before the security-only releases start.
Re: Rails 4.0: Release Candidate 1 released
#40Earlier quoted context omitted.
I did, yes, but I didn't have that issue.
Weird. Now, I have to manually configure my database.yml in order to make it work on Heroku. Btw, I upgraded from 4.0.0.beta1 to 4.0.0.rc1. 4.0.0.beta1 works fine on Heroku but I keep running into ActiveRecord problem after upgrading to 4.0.0.rc1.