Changes/Ruby on Rails 4.1

Ruby on Rails 4.1

Summary

Ruby on Rails 4.1 is the latest version of well know web framework written in Ruby.

Owner

• Name: Vít Ondruch, Josef Stříbný
• Email: vondruch@redhat.com, jstribny@redhat.com, ruby-sig@lists.fedoraproject.org
• Release notes owner:

Current status

• Targeted release: Fedora 21
• Last updated: 2014-05-02
• Tracker bug: #1081587

Detailed Description

The Ruby on Rails stack is evolving quickly and Fedora needs to keep pace with it. Therefore the whole Ruby on Rails stack should be updated from 4.0 in Fedora 20 to 4.1 (latest version) in Fedora 21. This will ensure that all the Ruby developers using Fedora have the latest and greatest RPM-packaged Ruby on Rails.

Benefit to Fedora

This update will keep Fedora up-to-date and will ensure that the current Ruby on Rails developers stay with us as they will get support for system-packaged Ruby on Rails of the latest version. Apart from that, update to Rails 4.1 will bring a new version of rubygem-tzinfo which is able to use the zoneinfo timezone database so the users will be able to benefit from the system updates of zoneinfo files.

Scope

• Proposal owners:

• The whole Rails stack has to be updated
• Some dependencies of the Rails stack will need update

The packages need to be created/updated:

Package name	Task	Status
rubygem-spring	Create	pass jstribny 1076516
rubygem-arel	Update to 5.0.0	pass jstribny 1022695
rubygem-tzinfo	Update to 1.1	pass jstribny 917630
rubygem-minitest	Update to 5.1	pass vondruch 950392
rubygem-actionview	Create	pass jstribny
rubygem-activesupport	Update to 4.1.x	pass jstribny
rubygem-actionpack	Update to 4.1.x	pass jstribny
rubygem-activemodel	Update to 4.1.x	pass jstribny
rubygem-activerecord	Update to 4.1.x	pass jstribny
rubygem-actionmailer	Update to 4.1.x	pass jstribny
rubygem-railties	Update to 4.1.x	pass jstribny
rubygem-rails	Update to 4.1.x	pass jstribny

• Other developers: Update Rails dependent packages to be working with Ruby on Rails 4.1

• Release engineering: Not needed.

• Policies and guidelines: Not needed

Upgrade/compatibility impact

Web applications build above Ruby on Rails framework might need to be updated. Official upstream upgrade guide might come handy: http://guides.rubyonrails.org/upgrading_ruby_on_rails.html

How To Test

• No special hardware is needed.
• To test Rails 4.1 from upstream:

gem install rails -v 4.1.0
rails new app
cd app && rails s

• Go to http://127.0.0.1:3000/ and make sure you are running Rails 4.0.x
• To test only Rails itself

yum install rubygem-{rails,sqlite3}
rails new app
cd app && rails s

• To test the complete feature including generating a new Rails app using RPM

su -c "yum install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,therubyracer,sdoc,spring}"
rails new app --skip-bundle && cd app
sed -i "s|# gem 'therubyracer'|gem 'therubyracer'|" Gemfile
rails s

• Go to http://127.0.0.1:3000/ and make sure you are running Rails 4.1.x

User Experience

• New version of Ruby on Rails (4.1) available
• The most significant Rails 4.1 features:
  • Spring application preloader
  • config/secrets.yml
  • Action Pack variants
  • Action Mailer previews
• Users will be able to use rubygem-tzinfo with the system zoneinfo database

Dependencies

• There are several packages, which depends on Ruby on Rails framework. All need to be tested an updated:
• These needs to be surely updated:
  • rubygem-haml-rails to 0.5.3

• openshift-origin-broker and any of rubygem-openshift-origin* gems might need to be updated and tested against Rails 4.1
  • Contact person: Krishna Raman <kraman@redhat.com> from OpenShift Origin team
• Following gems don't support Rails 4.1 right now and would be broken by the update:
  • rubygem-simple_form
  • rubygem-delayed_job -> updated in rawhide
  • rubygem-delayed_job_active_record -> updated in rawhide
  • rubygem-haml-rails -> updated in rawhide

• As Rails requires a new version of minitest (5.0.0), many of the gems in Fedora will fail in %check during the next rebuild. We would need to patch those gems and submit the changes upstream.
  • Discussion on the Ruby SIG mailing list about new minitest update: https://lists.fedoraproject.org/pipermail/ruby-sig/2014-March/001522.html

Contingency Plan

• Contingency mechanism: None needed. Rails stack won't be updated until all its dependencies are in Rawhide. After that, it will be a simple matter of updating the core packages (and their dependencies).
• Contingency deadline: N/A
• Blocks release? No

Documentation

• http://api.rubyonrails.org/
• http://brewhouse.io/blog/2013/12/17/whats-new-in-rails-4-1.html?brewPubStart=1

Release Notes

• http://weblog.rubyonrails.org/2014/4/8/Rails-4-1/
• http://guides.rubyonrails.org/4_1_release_notes.html