Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rails 4.0: Release Candidate 1 released

weblog.rubyonrails.org

Post reply on HN
Print view View original

21–30 of 58 posts

Re: Rails 4.0: Release Candidate 1 released

#21

Post by steveklabnik »

DanielRibeiro wrote: post #20
steveklabnik wrote: post #17

Earlier quoted context omitted.

Here's how, normally: 1) You take the commit referenced, like this: https://github.com/rails/rails/commit/f980289fd2c1b9073a94b5... 2) Right below the title, GitHub shows you which branches the commit is in. As you can see with that commit (the one that caused the problem), it's only in 3-2-stable. Therefore, not being in master, it wasn't ever in Rails 4, only in Rails 3.2. Since this was a security issue, it's poss…

Thanks Steven! I'll look into it. And thanks for all the great work you've been putting on Rails.

<3

Re: Rails 4.0: Release Candidate 1 released

#22

Post by mhartl »

zachgersh wrote: post #2

Weird that the skipped out on Hartl Tutorial in their announcement, it's actually been in Beta for awhile: http://ruby.railstutorial.org/ruby-on-rails-tutorial-book?ve...

Thanks for mentioning this. You're right that the beta book has been out for a while, and I've tried updating the Rails Tutorial for the release candidate as well, but the new RC breaks tons of tests in the sample application. I probably won't have time to figure out the cause of the breakage until after RailsConf is over, but I'll plan to get to this ASAP next week.

Re: Rails 4.0: Release Candidate 1 released

#23

Post by zachgersh »

mpd wrote: post #13
steveklabnik wrote: post #3

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…

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.

Why not post your whole gemfile as a gist? People in the HN community could definitely go through and start to check some of the dependencies for you :)

Re: Rails 4.0: Release Candidate 1 released

#24

Post by marcamillion »

steveklabnik wrote: post #3

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…

How do the major gems play with this RC? Namely Devise, CanCan, etc.? I was going to play with the beta, but I think I saw some potential integration issues with Devise and I decided it wasn't worth the trouble.

Re: Rails 4.0: Release Candidate 1 released

#25

Post by rafaelfranca »

marcamillion wrote: post #24
steveklabnik wrote: post #3

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…

How do the major gems play with this RC? Namely Devise, CanCan, etc.? I was going to play with the beta, but I think I saw some potential integration issues with Devise and I decided it wasn't worth the trouble.

Devise already has a rails4 branch with support to Rails 4 and we are planning to do a beta release soon

Re: Rails 4.0: Release Candidate 1 released

#26

Post by steveklabnik »

marcamillion wrote: post #24
steveklabnik wrote: post #3

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…

How do the major gems play with this RC? Namely Devise, CanCan, etc.? I was going to play with the beta, but I think I saw some potential integration issues with Devise and I decided it wasn't worth the trouble.

Most of the biggest ones have been working for a while, or have a branch where they're working in support.

I think this is one of the biggest advantages of Travis' uptake in the Ruby world, actually: it's really easy to test your gem against Rails master and put it in allow_failures, which means you can know if your gem is compatible, and occasionally show when a new commit introduces an incompatibility.

If you find any gems that don't work, please ping me and I'll investigate and send PRs; this is one of the advantages of my employer (Jumpstart Lab) paying for OSS work. The whole Ruby world wins. :)

Re: Rails 4.0: Release Candidate 1 released

#28

Post by elektronaut »

steveklabnik wrote: post #3

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.

Re: Rails 4.0: Release Candidate 1 released

#29

Post by marcamillion »

steveklabnik wrote: post #26
marcamillion wrote: post #24

Earlier quoted context omitted.

How do the major gems play with this RC? Namely Devise, CanCan, etc.? I was going to play with the beta, but I think I saw some potential integration issues with Devise and I decided it wasn't worth the trouble.

Most of the biggest ones have been working for a while, or have a branch where they're working in support. I think this is one of the biggest advantages of Travis' uptake in the Ruby world, actually: it's really easy to test your gem against Rails master and put it in allow_failures, which means you can know if your gem is compatible, and occasionally show when a new commit introduces an incompatibility. If you find…

Interesting. Thanks...will do :)

Re: Rails 4.0: Release Candidate 1 released

#30

Post by marcamillion »

rafaelfranca wrote: post #25
marcamillion wrote: post #24

Earlier quoted context omitted.

How do the major gems play with this RC? Namely Devise, CanCan, etc.? I was going to play with the beta, but I think I saw some potential integration issues with Devise and I decided it wasn't worth the trouble.

Devise already has a rails4 branch with support to Rails 4 and we are planning to do a beta release soon

Never noticed that...thanks!
Post reply on HN