From Fedora Project Wiki
Line 78: Line 78:
 
|-
 
|-
 
|rubygem-actioncable
 
|rubygem-actioncable
|Create
+
|Create (5.0.x)
 
|{{result|fail|jaruga}}
 
|{{result|fail|jaruga}}
 
|-
 
|-
Line 210: Line 210:
 
|-
 
|-
 
|rubygem-nio4r
 
|rubygem-nio4r
|Create
+
|Create (~> 1.2)
 
|{{result|fail|jaruga}} [https://bugzilla.redhat.com/show_bug.cgi?id=1315801 #1315801]
 
|{{result|fail|jaruga}} [https://bugzilla.redhat.com/show_bug.cgi?id=1315801 #1315801]
 
|-
 
|-

Revision as of 18:39, 28 June 2016


Ruby on Rails 5.0

Summary

Ruby on Rails 5.0 is the latest version of well known web framework written in Ruby.

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.2 in Fedora 24 to 5.0 (latest version) in Fedora 25. 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 5.0 will bring ActionCable (A new framework that seamlessly integrates WebSockets with the rest of your Rails application), API mode (You can create a new Rails application using rails new backend --api), ActionRecord attributes that can override, and exclusive use of rails CLI over Rake.

Scope

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

List up all the packages needed by Rails 5.0 to specified the scope. The tasks are estimated from the result of "bundle list" and "Gemfile.lock" after both installing rails, and creating new Rails app.

Package name Task Status
rubygem-actioncable Create (5.0.x)
Fail fail jaruga
rubygem-actionmailer Update to 5.0.x
Fail fail jaruga
rubygem-actionpack Update to 5.0.x
Fail fail jaruga
rubygem-actionview Update to 5.0.x
Fail fail jaruga
rubygem-activejob Update to 5.0.x
Fail fail jaruga
rubygem-activemodel Update to 5.0.x
Fail fail jaruga
rubygem-activerecord Update to 5.0.x
Fail fail jaruga
rubygem-activesupport Update to 5.0.x
Fail fail jaruga
rubygem-arel Update to 7.x
Fail fail jaruga
rubygem-builder No need to update
Pass pass jaruga
rubygem-byebug No need to update
Pass pass jaruga
rubygem-coffee-rails No need to update. Fix the build failure.
Fail fail jaruga
rubygem-coffee-script No need to update. Fix the build failure.
Fail fail jaruga
rubygem-coffee-script-source No need to update
Pass pass jaruga
rubygem-concurrent-ruby No need to update
Pass pass jaruga
rubygem-debug_inspector No need to update
Pass pass jaruga
rubygem-erubis No need to update
Pass pass jaruga
rubygem-execjs No need to update. Fix the build failure.
Fail fail jaruga
rubygem-ffi No need to update
Pass pass jaruga
rubygem-globalid Update to >= 0.3.6
Fail fail jaruga
rubygem-i18n No need to update
Pass pass jaruga
rubygem-jbuilder Update to ~> 2.5
Fail fail jaruga
rubygem-jquery-rails No need to update
Pass pass jaruga
rubygem-json No need to update
Pass pass jaruga
rubygem-loofah No need to update
Fail fail jaruga
rubygem-listen No need to update
Pass pass jaruga
rubygem-mail No need to update
Pass pass jaruga
rubygem-method_source No need to update
Pass pass jaruga
rubygem-mime-types Update to 3.1 (latest version) because of rubygem-mime-types-data
Fail fail jaruga
rubygem-mime-types-data Create? TODO
Fail fail jaruga
rubygem-mini_portile2 No need to update
Pass pass jaruga
rubygem-minitest No need to update
Pass pass jaruga
rubygem-multi_json No need to update
Pass pass jaruga
rubygem-nio4r Create (~> 1.2)
Fail fail jaruga
#1315801
rubygem-nokogiri No need to update
Pass pass jaruga
rubygem-pkg-config No need to update
Pass pass jaruga
rubygem-puma Create? (~> 3.0) TODO
Fail fail jaruga
rubygem-rack Update to 2.x
Fail fail jaruga
rubygem-rack-test No need to update
Pass pass jaruga
rubygem-rails Update to 5.0.x
Fail fail jaruga
rubygem-rails-deprecated_sanitizer No need to update
Pass pass jaruga
rubygem-rails-dom-testing No need to update
Pass pass jaruga
rubygem-rails-html-sanitizer No need to update
Pass pass jaruga
rubygem-railties Update to 5.0.x
Fail fail jaruga
rubygem-rb-fsevent Create? (~> 0.9) TODO
Fail fail jaruga
rubygem-rb-inotify No need to update
Pass pass jaruga
rubygem-sass No need to update. Fix the build failure.
Fail fail jaruga
rubygem-sass-rails No need to update
Pass pass jaruga
rubygem-spring No need to update
Pass pass jaruga
rubygem-spring-watcher-listen Create? (~> 2.0.0) TODO
Fail fail jaruga
rubygem-sprockets No need to update. Fix the build failure.
Fail fail jaruga
rubygem-sprockets-rails No need to update
Pass pass jaruga
rubygem-sqlite3 No need to update
Pass pass jaruga
rubygem-thor No need to update
Pass pass jaruga
rubygem-thread_safe No need to update
Pass pass jaruga
rubygem-tilt No need to update
Pass pass jaruga
rubygem-turbolinks Update to 5.x
Fail fail jaruga
rubygem-turbolinks-source Create? TODO
Fail fail jaruga
rubygem-tzinfo No need to update
Pass pass jaruga
rubygem-uglifier No need to update. Fix the build failure.
Fail fail jaruga
rubygem-web-console No need to update
Pass pass jaruga
rubygem-websocket-driver Update to ~> 0.6.1
Fail fail jaruga
rubygem-websocket-extensions No need to update
Pass pass jaruga
  • Other developers: Update Rails dependent packages to be working with Ruby on Rails 5.0
  • Release engineering: Not needed.
  • Policies and guidelines: Not needed
  • Trademark approval: N/A (not needed for this Change)

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 5.0 from upstream:
gem install rails -v 5.0.x
rails new app
cd app && rails s
dnf 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 "dnf install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,sdoc,spring,byebug,web-console} nodejs"
rails new app --skip-bundle && cd app
rails s

User Experience

  • New version of Ruby on Rails (5.0) available
  • The most significant Rails 5.0 features:
    • ActionCable: user can use WebSockets with the rest of your Rails application.
    • API mode: uesr can create a Rails application for API server easily with API mode.
    • Exclusive use of rails CLI over Rake. Add bin/rails test, bin/rails db:migrate. Now bin/rails is the one master command to rule them all.
    • ActionRecord attributes: user can override ActiveRecord attributes if needed.

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 5.0
    • Contact person: Krishna Raman <kraman@redhat.com> from OpenShift Origin team
  • Following gems don't support Rails 5.0 right now and would be broken by the update:
    • none now
  • As Rails requires Ruby >= 2.2.2, the platform less than the version can not use Rails 5.0.

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