From Fedora Project Wiki
< Changes
(→Scope) |
(Change to sytem wide change) |
||
| Line 164: | Line 164: | ||
<!-- 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?--> | ||
* Release engineering: | * Release engineering: Not needed. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
* Policies and guidelines: | * 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. --> | ||
| Line 227: | Line 227: | ||
* Contingency deadline: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Documentation == | == Documentation == | ||
| Line 252: | Line 252: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
Revision as of 13:35, 30 July 2013
Ruby on Rails 4.0
Summary
Ruby on Rails 4.0 is the latest version of well know web framework written in Ruby.
Owner
- Name: Vít Ondruch, Josef Stříbný
- Email: vondruch@redhat.com, jstribny@redhat.com, ruby-sig@lists.fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 20
- Last updated: 2013-07-30
- Tracker bug: <will be assigned by the Wrangler>
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 3.2 in Fedora 19 to 4.0 (latest version) in Fedora 20. 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, Rails 4.0 also bring improved functionality, speed. security and better modularization.
Scope
- Proposal owners:
- The whole Rails stack has to be updated
- New additional gems will have to be packaged
- Some dependencies of the Rails stack will need update
The packages need to be created/updated (this is probably not an exhaustive list):
| Package name | Task | Status |
|---|---|---|
| rubygem-i18n | Update to 0.6.4 | 915728 |
| rubygem-tzinfo | Update to 0.3.37 | 917630 |
| rubygem-atomic | Create | 960139 |
| rubygem-thread_safe | Needed by ActiveSupport; Needs review | 961375 |
| rubygem-activesupport | Update to 4.0.x |  |
| rubygem-rack | Update to 1.5.2 | 903613 |
| rubygem-actionpack | Update to 4.0.x | |
| rubygem-activemodel | Update to 4.0.x | |
| rubygem-arel | Update to 4.0.0 | 953809 |
| rubygem-activerecord-deprecated_finders-1.0.3.gem (100%) | Depends on Rails 4.0 | 961364 |
| rubygem-activerecord | Update to 4.0.x | |
| rubygem-mime-types | 1.19.3 in Fedora |  |
| rubygem-polyglot | 0.3.3 in Fedora | |
| rubygem-treetop | 1.4.12 in Fedora | |
| rubygem-mail | 2.5.3 in Fedora | |
| rubygem-actionmailer | Update to 4.0.x | |
| rubygem-thor | Update to 0.18.1 | 927600 |
| rubygem-railties | Update to 4.0.x | |
| rubygem-sprockets | ActionPack dropped this dep | |
| rubygem-sprockets-rails | Needs review | 986991 |
| rubygem-rails | Update to 4.0.x | |
- Other developers: Update Rails dependent packages to be working with Ruby on Rails 4.0
- 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.0 before they actually get into Rawhide, use:
gem install rails 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
- When all packages land in Rawhide, use:
yum install rubygem-{rails,sqlite3}
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
User Experience
- New version of Ruby on Rails (4.0) available
Dependencies
- There are several packages, which depends on Ruby on Rails framework. All need to be tested an updated.
- openshift-origin-broker and any of rubygem-openshift-origin* gems might need to be updated and tested against Rails 4.0
- Contact person: Krishna Raman <kraman@redhat.com> from OpenShift Origin team
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 8 core packages (and their dependencies).
- Contingency deadline: N/A
- Blocks release? No