Live data from Hacker News

Rails 4.0: Release Candidate 1 released

weblog.rubyonrails.org

31–40 of 58 posts

Re: Rails 4.0: Release Candidate 1 released

#31

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.

Awesome. Glad to hear it. Thanks for giving it an early run.

Re: Rails 4.0: Release Candidate 1 released

#33
post #13

Earlier 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.

schema_plus (https://github.com/lomba/schema_plus) is having issues with ActiveRecord changes (API changes, methods not existing any more that they remove/overwrite etc).

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

#34

Would it be possible to get a TL;DR version of any decently sized changes from 4.0beta -> 4.0rc1?

In general, things were deprecated or moved to a gem, but it's intended to be compatible.

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

#35

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…

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

#36

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…

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.

Re: Rails 4.0: Release Candidate 1 released

#37

Earlier 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.

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.

Re: Rails 4.0: Release Candidate 1 released

#39

Are 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.

Here's the maintenance policy: http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-f...

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

#40

Earlier 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.

I made this app fresh on rc1, so theoretically that's the difference. Steveklabnik/attendr is the repo if you want to poke at it.
Post reply on HN