Rails 1.1: Release Candidate 1 available

Posted by David March 22, 2006 @ 01:35 AM

It’s been roughly three months since the release of the big one-oh. That’s obviously an eternity in Rails time, so its about high time we’re getting ready for the release for 1.1. And boy, is this an exciting upgrade!

I do believe this is the biggest upgrade to Rails we’ve ever done. We have recorded about 500 fixes, tweaks, and new features in the changelogs. That’s a lot and that’s just counting major new features like RJS as one.

So with all these goodies, we want to make sure we launch without any obvious blunders or backwards compatibility breaking changes. This is why we’re doing a release candidate and why we need your help to test it.

Rails 1.1 is supposed to be just fully backwards compatible with 1.0, but we did change just a couple of defaults, see CHANGED DEFAULT notes in the changelogs. That means we want to test Rails 1.1 with as many 1.0 applications as possible.

To install the release candidate gems, you just need to do:

gem install rake
gem install rails --source http://gems.rubyonrails.org

Or you can just install the new Rake gem (Rails 1.1 depends on Rake 0.7) and then call rake freeze_edge. That’ll pull the latest Rails down from the Subversion repository and bind just that one application to it.

Or you can set svn:externals on vendor/ to be against http://dev.rubyonrails.org/svn/rails/tags/rel_1-1-0_RC1, if you want to pull it in through Subversion automatically.

Lots of options, no excuses. We really need your help to make sure the final release is as solid as Rails 1.0 was. And so we don’t need 1.1.1 two days later.

Once you have the latest Rails installed, you can do rake rails:update to get the latest scripts and the latest version of Prototype and script.aculo.us installed in public/javascripts. That’s about all the upgrading you need to do to existing applications.

Do note, though, that all plugins may not be upgraded to be compatible with Rails 1.1. Or you may indeed just have an old version of a plugin that has been updated. Keep an eye out for that.

If you’re wondering why to even bother with Rails 1.1, Scott Raymond currently has the best play-by-play overview of what’s new. We’ll be adding to that with more walkthroughs and hopefully movies around release time.

If you need more documentation, I strongly encourage you to pick up Chad Fowler’s Rails Recipe book. It’s currently out in its 3rd beta release and includes a bunch of great recipes on the new 1.1 features. Including RJS, polymorphic associations (and how to do better tagging with them), join models, integration testing, and more. You can get it as a PDF right now for $21.50.

So help us help you. Test Rails 1.1 with your existing applications. Try building new stuff with it. And let us know if something breaks in the process. We will be taking care of all heinous bugs before release. Thank you all!

Posted in Releases | 44 comments

Comments

Leave a response

  1. Ezra Zygmuntowicz on 22 Mar 01:38:

    Nice!

  2. Joe on 22 Mar 02:31:

    Awesome.

  3. Sergio Bayona on 22 Mar 02:34:

    I’ve been eagerly awaiting for the polymorphic associations.

    Honk that choo choo!

  4. Shanlalit on 22 Mar 02:39:

    Wow!

    Congrats and thanks to everyone in core team.

  5. Jon Maddox on 22 Mar 02:57:

    Yay!

  6. Joe on 22 Mar 02:58:

    Is there a URL for RTFM’ing for 1.1 RC1? It doesn’t appear api.rubyonrails.com nor edgedocs.planetargon.org are 1.1.

  7. Brian on 22 Mar 05:41:

    I updated to the latest version by using the command ‘gem install rails—source http://gems.rubyonrails.org’.

    I noticed that in the announcement on the DL, it said the changelist number was 4010, but when I installed it looks like I pulled down 4008: ‘Successfully installed rails-1.0.0.4008’

    Did I not get RoR 1.1 RC1? So far, no problems either way.

  8. David Heinemeier Hansson on 22 Mar 05:53:

    rails-1.0.0.4008 is the RC1, 4010 is just tagging it.

  9. Kevin Ballard on 22 Mar 07:21:

    A couple things.

    First, `rake freeze_edge` only gave me the lib dir of rails, so `rake rails:update` didn’t have any javascripts/scripts to update my app with.

    Second, Typo is pretty broken under 1.1RC1, and I’m not familiar enough with some of this stuff to know why. Once I installed the upload_progress plugin (and fiddled environment.rb to require it instead of enabling the previously-built-in upload progress), I get nice errors about the namespaces of my components – when trying to define Plugins::Textfilters::AmazonController I get told Plugins doesn’t exist. Yet in Rails 1.0 it does, and according to component docs it’s supposed to. I’m really not sure what to do about this. I tried removing Plugins:: from everything with search&replace, and got an interesting error that indicated that the line Sidebar.find_all_visible(...) actually tried to run find_all_visible on a completely different class. So basically I’m really confused. Perhaps Tobias could try getting Typo running with 1.1RC1? ;)

  10. Tomas Jogin on 22 Mar 09:14:

    Models in modules are still broken and that seems like a pretty big showstopper to me; but you know that, it’s on the Final Drive list.

  11. Piotr Usewicz on 22 Mar 09:17:

    Yay!!!

  12. Levent on 22 Mar 09:55:

    when i run ruby script\runner i get superclass mismatch for class OrderedOptions (TypeError)

    i used rake freeze_edge

  13. graham on 22 Mar 11:18:

    i know its off topic, but how are people hosting rails in production? afaik fastcgi is deprecated and webrick isn’t suitable for large scale deployments.

    Anyone know how 37signals host their stuff?

  14. Pelle on 22 Mar 11:23:

    I’m running Edge on my new discussion service Talk.org which I just launched. So far no real issues.

    I am using several of the new features including rjs, which is worth the upgrade alone.

  15. Pelle on 22 Mar 11:23:

    I’m running Edge on my new discussion service Talk.org which I just launched. So far no real issues.

    I am using several of the new features including rjs, which is worth the upgrade alone.

  16. Jamie Hill on 22 Mar 12:24:

    Good job guys. Appreciate the hard work.

  17. Jeremy Pinnix on 22 Mar 14:01:

    To view the CHANGELOG:

    http://dev.rubyonrails.org/svn/rails/trunk/railties/CHANGELOG

  18. Seth Thomas Rasmussen on 22 Mar 16:16:

    Lots of nice progression, great to see. Definitely hook up the namespaces for modules, though!

  19. Ruben on 22 Mar 16:28:

    Weehee!

  20. Stephen Bannasch on 22 Mar 17:08:

    I have rails 1.0 installed. After updating rake I tried the following:

    rails editor cd editor rake freeze_edge script/server

    which produced an error when it couldn’t find the file:

    vendor/rails/railties/configs/lighttpd.conf

    to copy into config/lighttpd.conf

    Problem:

    The freeze_edge task in framework.rake only checks out the lib directories in each framework but vendor/rails/railties/lib/commands/servers/lighttpd.rb is looking for vendor/rails/railties/configs/lighttpd.conf.

    I patched my Rails 1.0 rake freeze_edge task (rails-1.0.0/lib/tasks/framework.rake): by inserting the following line after line 46:

    system “svn export http://dev.rubyonrails.org/svn/rails/trunk/railties/configs vendor/rails/railties/configs #{revision_switch}” end

    After rm -rf vendor/rails/ and rake freeze_edge my script/server worked.

  21. dgm on 22 Mar 20:36:

    graham: I’m using SCGI for my eproduction servers…

  22. Phil on 22 Mar 22:14:

    If you’re getting a nasty namespace error with rake 0.7, you may have multiple rakes installed.

  23. Andre in LA on 23 Mar 18:45:

    Starting console in a fresh 1.1 app results in an error (windows XP, ruby 1.8.2, rake version 0.7.0, gem version 0.8.10, actionmailer (1.1.5.4008, 1.1.5, 1.1.4, 1.1.3), actionpack (1.11.2.4008, 1.11.2, 1.11.1, 1.11.0), actionwebservice (1.0.0.4008, 1.0.0, 0.9.4, 0.9.3), activerecord (1.13.2.4008, 1.13.2, 1.13.1, 1.13.0) activesupport (1.2.5.4008, 1.2.5, 1.2.4, 1.2.3)):

    C:\_files\_dl\dev\test11>ruby script\console Loading development environment. c:/_files/_dl/ruby/lib/ruby/1.8/irb/init.rb:151:in `parse_opts’: undefined metho d `upcase’ for nil:NilClass (NoMethodError) from c:/_files/_dl/ruby/lib/ruby/1.8/irb/init.rb:19:in `setup’ from c:/_files/_dl/ruby/lib/ruby/1.8/irb.rb:54:in `start’ from c:/_files/_dl/ruby/bin/irb:13

    Any suggestions?

    Thank you!

  24. Thomas C. Snide on 23 Mar 19:38:

    After loading 1.1, my app no longer starts. Here are the error messages:

    c:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5.4008/lib/active_support/depen dencies.rb:125:in `const_missing’: uninitialized constant LoadingModule (NameError) from ./script/../config/environment.rb:81 from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:18:in `re quire__’ from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:18:in `re quire’ from script/server:44

  25. David Heinemeier Hansson on 23 Mar 20:11:

    Please use http://dev.rubyonrails.org for bug reports.

  26. Rath on 23 Mar 21:16:

    I have just updated rails and added polymorphic associations but they lookk they are not working. I’m following the recipe 17 of “Rails Recipes” and I’m getting an “Unknown key(s): as” error. The associations work properly on the console. The problem occurs when I’m listing the items… perhaps the problem is pagination. Is this a bug or what should I do?

    Here is the log: C:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/core_ext/hash/keys.rb:48:in `assert_valid_keys’ C:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.13.2/lib/active_record/associations.rb:438:in `has_one_without_reflection’ (eval):5:in `has_one’ #{RAILS_ROOT}/app/models/person.rb:4 #{RAILS_ROOT}/app/controllers/company_controller.rb:7:in `list’ -e:3

  27. Ry Walker on 23 Mar 22:03:

    I’m getting errors after upgrade similar to posts above—is there an easy way to roll an app back to 1.0?

  28. Andre in LA on 23 Mar 23:01:

    David, please add a note next to this blog’s comment box:

    “Your comment will appear after a short delay. Please only submit it once.”

    and maybe a message on top of the page upon submit:

    “Your comment has been received and will appear on this page in a few minutes.”

    Thank you.

  29. Dag Nabbit on 24 Mar 18:58:

    Thanks David! Looks like there’s enough changes to justify a ‘1.5’ or ‘2.0’.

    I hope we have smaller & more frequent releases in the future. Particularly bugfix-only releases.

    Keep up the great work!

  30. zzdragon316@126.com on 27 Mar 01:37:

    It is Great!

  31. http://www.zzdragon.name/zzdragon316@126.com on 27 Mar 01:39:

    It is Great!

  32. andy5@y-dna.com on 27 Mar 21:27:

    What am I doing wrong?

    #rake --version
rake, version 0.7.0
# rails -v
Rails 1.0.0
# ruby -v
ruby 1.8.4 (2005-12-24) [i686-linux]
# gem install rake
Attempting local installation of 'rake'
Local gem file not found: rake*.gem
Attempting remote installation of 'rake'
Updating Gem source index for: 
http://gems.rubyforge.org
Successfully installed rake-0.7.0
Installing RDoc documentation for rake-0.7.0...
# gem install rails --source http://gems.rubyonrails.org
Attempting local installation of 'rails'
Local gem file not found: rails*.gem
Attempting remote installation of 'rails'
Updating Gem source index for: http://gems.rubyonrails.org
Install required dependency activesupport? [Yn]  y
Install required dependency activerecord? [Yn]  y
Install required dependency actionpack? [Yn]  y
Install required dependency actionmailer? [Yn]  y
Install required dependency actionwebservice? [Yn]  y
Successfully installed rails-1.0.0.4033
Successfully installed activesupport-1.2.5.4033
Successfully installed activerecord-1.13.2.4033
Successfully installed actionpack-1.11.2.4033
Successfully installed actionmailer-1.1.5.4033
Successfully installed actionwebservice-1.0.0.4033
Installing RDoc documentation for activesupport-1.2.5.4033...
Installing RDoc documentation for activerecord-1.13.2.4033...
Installing RDoc documentation for actionpack-1.11.2.4033...
Installing RDoc documentation for actionmailer-1.1.5.4033...
Installing RDoc documentation for actionwebservice-1.0.0.4033...
$ rails -v
Rails 1.0.0

    Huh? What happened to 1.1?!

  33. orlaa.com on 28 Mar 09:06:

    Nice!

  34. orlaa.com on 28 Mar 09:07:

    Nice!

  35. Mike on 28 Mar 13:25:

    I successfully upgraded to Rails 1.1., but now when I point my browser to localhost:3000, I get a the following:

    Routing Error

    Recognition failed for ”/rails_info/properties”

    What’s the best fix for this?

  36. Ben Wolf on 28 Mar 20:10:

    Did anybody respond to the issue that Thomas described? I’m having the same problem with my applicactions. I have several client apps that won’t start.

  37. Frustated User on 28 Mar 21:53:

    Hi,

    I have the same error as 24).

    Very unprofessional.

    Do you know QA ?

    Such large screwups doesn’t happen with PHP.

    And PHP works flawlessly with IIS without thirdparty plugins(URL rewriting)

    I have to think twice to use Rails in a professional project.

    For amateur student project it’s fine as those screwups doesn’t matter there.

    cya

  38. Chris Alexander on 29 Mar 00:27:

    I am having the same issues as Thomas as well. Some feedback as to why this is happening would certainly be appreciated.

  39. Widi Harsojo on 29 Mar 04:13:

    Hi, I See on No. 35 like mine but I can work-it out :-),

    I run rubyonrail on fedora core 5 installation, and it already have ruby 1.8.4 on it, but some of the files in ruby distribution are missing in folder ”/usr/lib/ruby/1.8” like, rdoc and irb, you can compare it with instantrails distribution on that folder or you can install ruby 1.8.4 from the source

    Cheerrrssssss…... rails rock!

  40. Claudio Perez Gamayo on 30 Mar 14:46:

    Hi, updated all my apps and working fine here. Thank you.

  41. kyutums on 31 Mar 14:41:

    I followed what another site said and got my project working again:

    You can re-run the (new version of the) “rails” command on your project (“rails .” when your working directory is your RAILS_ROOT). Allow it to overwrite any file you haven’t customized, and that should fix it.

    From http://www.forbiddenweb.org/viewtopic.php?id=86290

  42. kyutums on 31 Mar 14:41:

    I followed what another site said and got my project working again:

    You can re-run the (new version of the) “rails” command on your project (“rails .” when your working directory is your RAILS_ROOT). Allow it to overwrite any file you haven’t customized, and that should fix it.

    From http://www.forbiddenweb.org/viewtopic.php?id=86290

  43. Moz on 31 Mar 16:44:

    ruby script\console doesn’t seem to work anymore.

    I get:

    Loading development environment. c:/ruby/lib/ruby/1.8/irb/init.rb:151:in `parse_opts’: undefined method `upcase’ for nil:NilClass (NoMethodError) from c:/ruby/lib/ruby/1.8/irb/init.rb:19:in `setup’ from c:/ruby/lib/ruby/1.8/irb.rb:54:in `start’ from c:/ruby/bin/irb:13

  44. Joseph Riesen on 08 Apr 00:32:

    Kind of ironic that Rails 1.1.1 came out less than a week later than 1.1.0. Not that I mind – release early, and often! =)

Ruby on Rails was created by David Heinemeier Hansson, a partner at 37signals,
then extended and improved by a core team of committers and hundreds of open-source contributors.

Rails is released under the MIT license. Ruby under the Ruby License.

"Rails", "Ruby on Rails", and the Rails logo are trademarks of David Heinemeier Hansson. All rights reserved.

Sponsored by

 37signals