Features/Rails 3.2

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Moved to FeatureReadyForFesco, ticket #886)
Line 65: Line 65:
  
  
[[Category:FeatureReadyForWrangler]]
+
[[Category:FeatureReadyForFesco]]
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Revision as of 12:50, 9 July 2012

Contents

Rails 3.2

Summary

Rails 3.2 is the latest version of Ruby on Rails stack. Fedora 17 still contains Rails 3.0, which are rather old from the Rails community point of view.

Owner

  • Email: <bkabrda@redhat.com>

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-6-21
  • Percentage of completion: 0%

Detailed Description

The Rails stack is evolving quickly and Fedora needs to keep pace with it. Therefore the whole Rails stack should be updated from 3.0 in Fedora 17 to 3.2 (latest version) in Fedora 18. This will ensure that all the Ruby developers using Fedora have the latest and greatest RPM-packaged Rails.

Benefit to Fedora

This update will keep Fedora up-to-date and will ensure that the current Rails developers stay with us as they will get support for system-packaged Rails of the latest version. Apart from that, Rails 3.2 also bring improved functionality, speed and security.

Scope

  • The whole Rails stack has to be updated (8 packages)
  • Additional 8 Gems will have to be packaged
  • Circa 15 more packages will need update

This update will only affect the RPM-packaged RubyGems with no effect on Ruby itself nor any other languages.

How To Test

  • No special hardware is needed.
  • To test Rails 3.2 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 3.2.x
  • When all packages land in Rawhide, use:
yum install rubygem-{rails,sqlite3}
rails new app
cd app && rails s

User Experience

Ruby programmers will once again be able to develop using RPM-packaged Rails of the newest version, using all its advantages.

Dependencies

Apart from those mentioned in #Scope, all the packages from the Rails stack are dependencies of other cca 50 packages. These will have to be rebuilt and possibly updated.

Contingency Plan

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 packages (and their dependencies).

Documentation

Release Notes

Comments and Discussion