From Fedora Project Wiki
< Changes
| 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. | = Ruby on Rails 4.2 <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
| Line 33: | 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: | * 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: | * 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: <!--- 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) | ||
| Line 42: | Line 42: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * 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 56: | Line 56: | ||
== 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. | 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. | 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 161: | Line 161: | ||
* To test Rails 4.1 from upstream: | * To test Rails 4.1 from upstream: | ||
<pre> | <pre> | ||
gem install rails -v 4. | gem install rails -v 4.2.0 | ||
rails new app | rails new app | ||
cd app && rails s | cd app && rails s | ||
| Line 179: | Line 179: | ||
rails s | rails s | ||
</pre> | </pre> | ||
* Go to http://127.0.0.1:3000/ and make sure you are running Rails 4. | * 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. | * New version of Ruby on Rails (4.2) available | ||
* The most significant Rails 4. | * The most significant Rails 4.2 features: | ||
** | ** ActiveJob | ||
** | ** ActionMailer #deliver_later | ||
** | ** GlobalID | ||
** | ** Web Console | ||
== Dependencies == | == Dependencies == | ||
| Line 225: | Line 225: | ||
<!-- 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 234: | Line 234: | ||
--> | --> | ||
* http://weblog.rubyonrails.org/2014/4/8/Rails-4- | * http://weblog.rubyonrails.org/2014/4/8/Rails-4-2/ | ||
* http://guides.rubyonrails.org/ | * http://guides.rubyonrails.org/4_2_release_notes.html | ||
<!-- [[Category:ChangeAcceptedF21]] --> | <!-- [[Category:ChangeAcceptedF21]] --> | ||
Revision as of 11:16, 30 September 2014
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
- Name: Josef Stříbný, Vít Ondruch
- Email: jstribny@redhat.com, vondruch@redhat.com, ruby-sig@lists.fedoraproject.org
- Release notes 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-spring | Create | 1076516 |
| rubygem-arel | Update to 5.0.0 | 1022695 |
| rubygem-tzinfo | Update to 1.1 | 917630 |
| rubygem-minitest | Update to 5.1 | 950392 |
| rubygem-actionview | Create | |
| rubygem-activesupport | Update to 4.1.x | |
| rubygem-actionpack | Update to 4.1.x | |
| rubygem-activemodel | Update to 4.1.x | |
| rubygem-activerecord | Update to 4.1.x | |
| rubygem-actionmailer | Update to 4.1.x | |
| rubygem-railties | Update to 4.1.x | |
| rubygem-rails | Update to 4.1.x |
- 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.2.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.2.x
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:
- 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