kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Some improvements to the release notes

Browse source
This commit is contained in:
Pratik Naik 2010-02-03 12:30:35 +00:00
parent 2f1657cb6c
commit 69d0e94da5
1 changed files with 11 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
railties/guides/source/3_0_release_notes.textile
View file

@ -1,4 +1,4 @@
h2. Ruby on Rails 3.0 Beta Release Notes
h2. Ruby on Rails 3.0 Release Notes
Rails 3.0 is a landmark release as it delivers on the Merb/Rails merge promise made in December 2008. Rails 3.0 provides major upgrades to all of the components of Rails, including a complete overhaul of the router and query APIs.
@ -10,39 +10,34 @@ These release notes cover the major upgrades, but don't include every little bug
endprologue.
WARNING: These release notes are still being modified constantly. Rails 3.0 beta is not out yet, so be sure to check back here on the actual release date to find any changes. Comments and corrections welcome, please drop by #docrails ( irc.freenode.net ) or contribute via "docrails":http://github.com/lifo/docrails/.
WARNING: These release notes are still being modified constantly. Rails 3.0 beta is not out yet, so be sure to check back here on the actual release date to find any changes. Comments and corrections welcome, please send to "Mikel Lindsaar":http://lindsaar.net or "@raasdnil"::http://twitter.com/raasdnil or contribute via "docrails":http://github.com/lifo/docrails/.
h3. Upgrading from Rails 2.3.5 to Rails 3
h3. Upgrading from Rails 2.3.5 to Rails 3.0
As always, having a high coverage, passing test suite is your friend when upgrading. You should also first upgrade to Rails 2.3.5 and make sure your application still runs as expected before attempting to update to Rails 3. In general, the upgrade from Rails 2.x to Rails 3 centres around three big changes:
As always, having a high coverage, passing test suite is your friend when upgrading. You should also first upgrade to Rails 2.3.5 and make sure your application still runs as expected before attempting to update to Rails 3.0. In general, the upgrade from Rails 2.x to 3.0 centers around three big changes:
h4. Ruby 1.8.6 no longer supported
Rails 3 requires Ruby 1.8.7 or higher. Ruby 1.9.2 is now fully supported as well. Support for all of the previous Ruby versions has been dropped officially and you should upgrade as early as possible.
h4. New Ruby Version Requirement
h4. Rails Application object
WARNING: Rails 3.0 was built to run on Ruby version 1.8.7. Support for previous versions of Ruby has been dropped and Rails 3.0 will no longer boot on any of these versions.
As part of the groundwork for supporting running multiple Rails applications in the same process, Rails 3 introduces the concept of an Application object. An application object holds all the application specific configurations and is very similar in nature to +config/environment.rb+ from the previous versions of Rails.
Each Rails application now must have a corresponding application object. Application object is typically defined in +config/application.rb+. If you're upgrading an existing application to Rails 3, you must add this file and move the appropriate configurations from +config/environment.rb+ to +config/application.rb+.
h4. The new boot process
As part of the shift to treating Rails apps as Rack endpoints, you are now required to have a +config/application.rb+ file, which takes over much of the work +config/environment.rb+ used to handle. Along with that comes a lot of internal change to the boot process, but those changes are mostly internal.
h4. New rails binary
h4. script/* replaced by script/rails
The +rails+ binary has been upgraded in Rails 3.0 It lives as <tt>script/rails</tt> and is a one stop command for all of the commands that used to live in <tt>script/</tt>. You now call <tt>rails <command_name></tt> instead.
h4. Gems and gems and gems
h4. Dependencies and config.gem
The +config.gem+ method is gone and has been replaced by using +bundler+ and a +Gemfile+, see "Vendoring Gems":#vendoring-gems below.
h4. New APIs
Both the router and query interface have seen significant, breaking changes. There is a backwards compatibility layer that is in place and will be supported until the 3.1 release.
h4. Upgrade Process
To help with the upgrade process, a plugin named "Rails Upgrade":http://github.com/rails/rails_upgrade has been created to automate part of it.