From Fedora Project Wiki

< Changes

Revision as of 16:56, 22 January 2015 by Vondruch (talk | contribs)


Ruby on Rails 4.2

Summary

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

Note: This change might be changed to Rails 5.

Owner

Current status

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.1 in Fedora 21 to 4.2 (latest version) in Fedora 22. 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.2 will bring ActiveJob (an adapter layer on top of queuing systems like Resque, Delayed Job, Sidekiq), ActionMailer #deliver_later, GlobalID serialization and Web Console (an IRB console available in the browser).

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-activejob Create
rubygem-globalid Create
Pass pass jstribny
#1179133
rubygem-web-console Create
rubygem-rails-dom-testing Create
Inprogress inprogress vondruch
#1184920
rubygem-rails-deprecated_sanitizer Create
Inprogress inprogress vondruch
#1184130
rubygem-rails-html-sanitizer Create
Inprogress inprogress vondruch
[#1184996
rubygem-binding_of_caller Create
rubygem-debug_inspector Create #960056
rubygem-sprockets-rails Update to 3.x
rubygem-sass-rails Update to 5.x
rubygem-arel Update to 6.x
rubygem-i18n Update to 0.7.x
Pass pass vondruch
#1176976
rubygem-rack Update to 1.6.0
rubygem-actionview Update to 4.2.x
rubygem-activesupport Update to 4.2.x
rubygem-actionpack Update to 4.2.x
rubygem-activemodel Update to 4.2.x
rubygem-activerecord Update to 4.2.x
rubygem-actionmailer Update to 4.2.x
rubygem-railties Update to 4.2.x
rubygem-rails Update to 4.2.x
  • Other developers: Update Rails dependent packages to be working with Ruby on Rails 4.2
  • 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.2 from upstream:
gem install rails -v 4.2.0
rails new app
cd app && rails s
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

User Experience

  • New version of Ruby on Rails (4.2) available
  • The most significant Rails 4.2 features:
    • ActiveJob
    • ActionMailer #deliver_later
    • GlobalID
    • Web Console

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:
    • none now
  • openshift-origin-broker and any of rubygem-openshift-origin* gems might need to be updated and tested against Rails 4.2
    • Contact person: Krishna Raman <kraman@redhat.com> from OpenShift Origin team
  • Following gems don't support Rails 4.2 right now and would be broken by the update:
    • none now
  • 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.

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

Release Notes