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...")
 
 
(38 intermediate revisions by 4 users not shown)
Line 20: Line 20:
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
  
= Ruby on Rails 4.1 <!-- The name of your change proposal --> =
+
= Ruby on Rails 4.2 <!-- The name of your change proposal --> =
  
 
== Summary ==
 
== Summary ==
 
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
 
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
Ruby on Rails 4.1 is the latest version of well know web framework written in Ruby.
+
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 ==
 
== Owner ==
Line 31: Line 33:
 
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:vondruch| Vít Ondruch]], [[User:jstribny| Josef Stříbný]]
+
* Name: [[User:jstribny| Josef Stříbný]], [[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: vondruch@redhat.com, jstribny@redhat.com, ruby-sig@lists.fedoraproject.org
+
* Email: jstribny@redhat.com, vondruch@redhat.com, ruby-sig@lists.fedoraproject.org
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
+
* Release notes owner: [mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])
 +
<!--- 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 40: Line 43:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/21 | Fedora 21 ]]  
+
* Targeted release: [[Releases/22 | Fedora 22 ]]  
 
* 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 50: Line 53:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1081587 #1081587] <!-- [https://bugzilla.redhat.com/show_bug.cgi?id=998578 #998578] -->
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1184910 #1184910]
  
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
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.  
+
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 ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
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.
+
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 ==
 
== Scope ==
Line 76: Line 79:
 
! Status
 
! Status
 
|-
 
|-
|rubygem-spring
+
|rubygem-activejob
 
|Create  
 
|Create  
|{{result|pass|jstribny}} [https://bugzilla.redhat.com/show_bug.cgi?id=1076516 1076516]
+
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1185308 #1185308]
 +
|-
 +
|rubygem-globalid
 +
|Create
 +
|{{result|pass|jstribny}} [https://bugzilla.redhat.com/show_bug.cgi?id=1179133 #1179133]
 +
|-
 +
|rubygem-web-console
 +
|Create
 +
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1186351 #1186351]
 +
|-
 +
|rubygem-rails-dom-testing
 +
|Create
 +
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1184920 #1184920]
 +
|-
 +
|rubygem-rails-deprecated_sanitizer
 +
|Create
 +
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1184130 #1184130]
 +
|-
 +
|rubygem-rails-html-sanitizer
 +
|Create
 +
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1184996 #1184996]
 +
|-
 +
| rubygem-binding_of_caller
 +
|Create
 +
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1185957 #1185957]
 +
|-
 +
| rubygem-debug_inspector
 +
|Create
 +
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=960056 #960056]
 +
|-
 +
|rubygem-sass-rails
 +
|Update to 5.x
 +
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-arel
 
|rubygem-arel
|Update to 5.0.0
+
|Update to 6.x
|{{result|pass|jstribny}} [https://bugzilla.redhat.com/show_bug.cgi?id=1022695 1022695]
+
|{{result|pass|jstribny}}
 
|-
 
|-
|rubygem-tzinfo
+
|rubygem-i18n
|Update to 1.1
+
|Update to 0.7.x
|{{result|pass|jstribny}} [https://bugzilla.redhat.com/show_bug.cgi?id=917630 917630]
+
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=1176976 #1176976]
 
|-
 
|-
|rubygem-minitest
+
|rubygem-rack
|Update to 5.1
+
|Update to 1.6.0
|{{result|pass|vondruch}} [https://bugzilla.redhat.com/show_bug.cgi?id=950392 950392]
+
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-actionview
 
|rubygem-actionview
|Create
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-activesupport
 
|rubygem-activesupport
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-actionpack
 
|rubygem-actionpack
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-activemodel
 
|rubygem-activemodel
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-activerecord
 
|rubygem-activerecord
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-actionmailer
 
|rubygem-actionmailer
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-railties
 
|rubygem-railties
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|-
 
|-
 
|rubygem-rails
 
|rubygem-rails
|Update to 4.1.x
+
|Update to 4.2.x
 
|{{result|pass|jstribny}}
 
|{{result|pass|jstribny}}
 
|}
 
|}
  
* Other developers: Update Rails dependent packages to be working with Ruby on Rails 4.1 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Other developers: Update Rails dependent packages to be working with Ruby on Rails 4.2 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
Line 157: Line 192:
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* No special hardware is needed.
 
* No special hardware is needed.
* To test Rails 4.1 from upstream:
+
* To test Rails 4.2 from upstream:
 
<pre>
 
<pre>
gem install rails -v 4.1.0
+
gem install rails -v 4.2.0
 
rails new app
 
rails new app
 
cd app && rails s
 
cd app && rails s
 
</pre>
 
</pre>
* Go to http://127.0.0.1:3000/ and make sure you are running Rails 4.0.x
+
* Go to http://127.0.0.1:3000/ and make sure you are running Rails 4.2.x
 
* To test only Rails itself
 
* To test only Rails itself
 
<pre>
 
<pre>
Line 172: Line 207:
 
* To test the complete feature including generating a new Rails app using RPM
 
* To test the complete feature including generating a new Rails app using RPM
 
<pre>
 
<pre>
su -c "yum install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,therubyracer,sdoc,spring}"
+
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
 
sed -i "s|# gem 'therubyracer'|gem 'therubyracer'|" Gemfile
 
rails s
 
rails s
 
</pre>
 
</pre>
* Go to http://127.0.0.1:3000/ and make sure you are running Rails 4.1.x
+
* Go to http://127.0.0.1:3000/ and make sure you are running Rails 4.2.x
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* New version of Ruby on Rails (4.1) available
+
* New version of Ruby on Rails (4.2) available
* The most significant Rails 4.1 features:
+
* The most significant Rails 4.2 features:
** Spring application preloader
+
** ActiveJob
** config/secrets.yml
+
** ActionMailer #deliver_later
** Action Pack variants
+
** GlobalID
** Action Mailer previews
+
** Web Console
* Users will be able to use rubygem-tzinfo with the system zoneinfo database
 
  
 
== Dependencies ==
 
== Dependencies ==
Line 194: Line 228:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
 
* There are several packages, which depends on Ruby on Rails framework. All need to be tested an updated:
 
* There are several packages, which depends on Ruby on Rails framework. All need to be tested an updated:
 
* These needs to be surely updated:
 
* These needs to be surely updated:
** rubygem-haml-rails to 0.5.3
+
** none now
 
+
* openshift-origin-broker and any of rubygem-openshift-origin* gems might need to be updated and tested against Rails 4.2
* 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
 
** 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:
+
* Following gems don't support Rails 4.2 right now and would be broken by the update:
** rubygem-simple_form
+
** none now
** 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.
 
* 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
 
** Discussion on the Ruby SIG mailing list about new minitest update: https://lists.fedoraproject.org/pipermail/ruby-sig/2014-March/001522.html
Line 223: Line 251:
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* http://api.rubyonrails.org/
 
* http://api.rubyonrails.org/
* http://brewhouse.io/blog/2013/12/17/whats-new-in-rails-4-1.html?brewPubStart=1
+
<!-- * http://brewhouse.io/blog/2013/12/17/whats-new-in-rails-4-1.html?brewPubStart=1 -->
  
 
== Release Notes ==
 
== Release Notes ==
Line 232: Line 260:
 
-->
 
-->
  
* http://weblog.rubyonrails.org/2014/4/8/Rails-4-1/
+
* http://weblog.rubyonrails.org/2014/4/8/Rails-4-2/
* http://guides.rubyonrails.org/4_1_release_notes.html
+
* http://guides.rubyonrails.org/4_2_release_notes.html
  
 
<!--  [[Category:ChangeAcceptedF21]] -->
 
<!--  [[Category:ChangeAcceptedF21]] -->
Line 243: Line 271:
 
<!-- Select proper category, default is Self Contained Change -->
 
<!-- Select proper category, default is Self Contained Change -->
 
<!-- [[Category:SelfContainedChange]] -->
 
<!-- [[Category:SelfContainedChange]] -->
[[Category:SystemWideChange]]
+
[[Category:SystemWideChange]] [[Category:ChangeAcceptedF22]]

Latest revision as of 14:42, 16 February 2015


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
Pass pass vondruch
#1185308
rubygem-globalid Create
Pass pass jstribny
#1179133
rubygem-web-console Create
Pass pass vondruch
#1186351
rubygem-rails-dom-testing Create
Pass pass vondruch
#1184920
rubygem-rails-deprecated_sanitizer Create
Pass pass vondruch
#1184130
rubygem-rails-html-sanitizer Create
Pass pass vondruch
#1184996
rubygem-binding_of_caller Create
Pass pass vondruch
#1185957
rubygem-debug_inspector Create
Pass pass vondruch
#960056
rubygem-sass-rails Update to 5.x
Pass pass jstribny
rubygem-arel Update to 6.x
Pass pass jstribny
rubygem-i18n Update to 0.7.x
Pass pass vondruch
#1176976
rubygem-rack Update to 1.6.0
Pass pass jstribny
rubygem-actionview Update to 4.2.x
Pass pass jstribny
rubygem-activesupport Update to 4.2.x
Pass pass jstribny
rubygem-actionpack Update to 4.2.x
Pass pass jstribny
rubygem-activemodel Update to 4.2.x
Pass pass jstribny
rubygem-activerecord Update to 4.2.x
Pass pass jstribny
rubygem-actionmailer Update to 4.2.x
Pass pass jstribny
rubygem-railties Update to 4.2.x
Pass pass jstribny
rubygem-rails Update to 4.2.x
Pass pass jstribny
  • 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,byebug,web-console}"
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