From Fedora Project Wiki
(Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...")
 
No edit summary
Line 31: Line 31:
This should link to your home wiki page so we know who you are.  
This should link to your home wiki page so we know who you are.  
-->
-->
* Name: [[User:pvalena| Pavel Valena]], [[User:jaruga| Jun Aruga]], [[User:vondruch| Vít Ondruch]]
* Name: [[User:jaruga| Jun Aruga]], [[User:pvalena| Pavel Valena]], [[User:vondruch| Vít Ondruch]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: pvalena@redhat.com, jaruga@redhat.com, vondruch@redhat.com, ruby-sig@lists.fedoraproject.org
* Email: jaruga@redhat.com, pvalena@redhat.com, vondruch@redhat.com, ruby-sig@lists.fedoraproject.org
* Release notes owner: [mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]]) '''TODO'''
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 41: Line 40:


== Current status ==
== Current status ==
* Targeted release: [[Releases/25 | Fedora 25 ]] '''TODO'''
* Targeted release: [[Releases/25 | Fedora 25 ]]
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 107: Line 106:
|rubygem-activesupport
|rubygem-activesupport
|Update to 5.0.x
|Update to 5.0.x
|{{result|fail|jaruga}}
|-
|rubygem-arel
|Update? '''TODO'''
|{{result|fail|jaruga}}
|{{result|fail|jaruga}}
|-
|-
Line 172: Line 167:
|Create
|Create
|{{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]
|-
|rubygem-nokogiri
|Update? '''TODO'''
|{{result|fail|jaruga}}
|-
|-
|rubygem-nokogiri
|rubygem-nokogiri
Line 250: Line 241:
* Policies and guidelines: Not needed  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: Not needed  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
Line 283: Line 277:
* To test only Rails itself
* To test only Rails itself
<pre>
<pre>
yum install rubygem-{rails,sqlite3}
dnf install rubygem-{rails,sqlite3}
rails new app
rails new app
cd app && rails s
cd app && rails s
</pre>
</pre>
* To test the complete feature including generating a new Rails app using RPM '''TODO''' not therubyracer but nodejs?
* To test the complete feature including generating a new Rails app using RPM
<pre>
<pre>
sudo dnf install nodejs
su -c "dnf install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,sdoc,spring,byebug,web-console} nodejs"
su -c "yum install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,therubyracer,sdoc,spring,byebug,web-console}"
rails new app --skip-bundle && cd app
rails new app --skip-bundle && cd app
sed -i "s|# gem 'therubyracer'|gem 'therubyracer'|" Gemfile
rails s
rails s
</pre>
</pre>
Line 345: Line 337:
* http://edgeguides.rubyonrails.org/5_0_release_notes.html
* http://edgeguides.rubyonrails.org/5_0_release_notes.html


<!--  [[Category:ChangeAcceptedF21]] -->
[[Category:ChangePageIncomplete]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 353: Line 345:
<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SelfContainedChange]] -->
[[Category:SystemWideChange]] [[Category:ChangeAcceptedF25]]
[[Category:SystemWideChange]]

Revision as of 05:54, 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

The packages need to be created/updated:

Package name Task Status
rubygem-actioncable Create
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? TODO
Fail fail jaruga
rubygem-builder Update? TODO
Fail fail jaruga
rubygem-concurrent-ruby Update? TODO
Fail fail jaruga
rubygem-erubis Update? TODO
Fail fail jaruga
rubygem-globalid Update? TODO
Fail fail jaruga
rubygem-i18n Update? TODO
Fail fail jaruga
rubygem-json Update? TODO
Fail fail jaruga
rubygem-loofah Update? TODO
Fail fail jaruga
rubygem-mail Update? TODO
Fail fail jaruga
rubygem-method_source Update? TODO
Fail fail jaruga
rubygem-mime-types Update? TODO
Fail fail jaruga
rubygem-mime-types-data Create? TODO
Fail fail jaruga
rubygem-mini_portile2 Update? TODO
Fail fail jaruga
rubygem-minitest Update? TODO
Fail fail jaruga
rubygem-nio4r Create
Fail fail jaruga
#1315801
rubygem-nokogiri Update? TODO
Fail fail jaruga
rubygem-pkg-config Update? TODO
Fail fail jaruga
rubygem-rack Update? TODO
Fail fail jaruga
rubygem-rack-test Update? TODO
Fail fail jaruga
rubygem-rails Update to 5.0.x
Fail fail jaruga
rubygem-rails-deprecated_sanitizer Update? TODO
Fail fail jaruga
rubygem-rails-dom-testing Update? TODO
Fail fail jaruga
rubygem-rails-html-sanitizer Update? TODO
Fail fail jaruga
rubygem-railties Update to 5.0.x
Fail fail jaruga
rubygem-sprockets Update? TODO
Fail fail jaruga
rubygem-sprockets-rails Update? TODO
Fail fail jaruga
rubygem-thor Update? TODO
Fail fail jaruga
rubygem-thread_safe Update? TODO
Fail fail jaruga
rubygem-tzinfo Update? TODO
Fail fail jaruga
rubygem-websocket-driver Update? TODO
Fail fail jaruga
rubygem-websocket-extensions Update? TODO
Fail fail 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