Have there been rails 3.2 rpms built? And what do Rails 3.0 -> 3.2 upgrade stories look like upstream? Might be worth considering holding this off for another Fedora release or two to let things shore up / settle down.

-Mo

On 06/21/2012 10:59 AM, Guillermo Gómez wrote:

Please do.... :)

honestly im not using rails from fedora, yes its old but we are seeing so many releases in such a short time thats challenging to keep up with 3.2.x , please jump directly to 3.2.6

Guillermo

On Thu, Jun 21, 2012 at 2:39 AM, Bohuslav Kabrda bkabrda@redhat.com wrote:

...

Hi all, I just created a feature page for Rails 3.2 in Fedora 18 [1] - I figured we will need to update, as the current 3.0 is getting quite old (I'm assuming nobody is against this, right?). I'd be glad if you could give me some comments and suggestions before submitting the feature to FESCo.

Thanks.

-- Regards, Bohuslav "Slavek" Kabrda.

[1] https://fedoraproject.org/wiki/Features/Rails_3.2 _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

Sorry for the belated response. It seems like there are a few API changes but nothing that we can't handle so no objections to updating from here.

-Mo

On 06/26/2012 01:39 AM, Bohuslav Kabrda wrote:

Hey Mo, just googling around randomly, it seems that there are no problems with upgrade to Rails 3.2. I have already built 3.2.3 as an SCL [1] and run it with no problems whatsoever.

Slavek.

[1] https://fedorahosted.org/SoftwareCollections/

----- Original Message -----

...

Have there been rails 3.2 rpms built? And what do Rails 3.0 -> 3.2 upgrade stories look like upstream? Might be worth considering holding this off for another Fedora release or two to let things shore up / settle down.

-Mo

On 06/21/2012 10:59 AM, Guillermo Gómez wrote:

...

Please do.... :)

honestly im not using rails from fedora, yes its old but we are seeing so many releases in such a short time thats challenging to keep up with 3.2.x , please jump directly to 3.2.6

Guillermo

On Thu, Jun 21, 2012 at 2:39 AM, Bohuslav Kabrda bkabrda@redhat.com wrote:

...

Hi all, I just created a feature page for Rails 3.2 in Fedora 18 [1] - I figured we will need to update, as the current 3.0 is getting quite old (I'm assuming nobody is against this, right?). I'd be glad if you could give me some comments and suggestions before submitting the feature to FESCo.

Thanks.

-- Regards, Bohuslav "Slavek" Kabrda.

[1] https://fedoraproject.org/wiki/Features/Rails_3.2 _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

---

ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

----- Original Message -----

So, the Rails 3.2 Feature has been approved on last fesco meeting. Me and Vit have already started working on the first packages that need to be created before actually updating the Rails packages. On the feature page [1], you can find a list of what has to be updated and packaged for the Rails 3.2 stack. If you'd like to help, feel free to assign yourself by writing your name to the table in [2] and don't forget to update the status of your task. Also, some updates and rebuilds (to run the tests with updated versions) of the dependent packages will be needed. Find them in [3]. I'd like to ask all of you to update/rebuild your packages when the updated dependencies are built. One minor issue: rubygem-scruffy claims that it needs bundler < 3, but Rails 3.2 need bundler > 3. So it will either have to be patched (at least the gemspec) to work with new bundler or deprecated. There have been no new versions of scruffy for more than one year. Scruffy is owned by mmorsi, so Mo, could you please have a look at it?

And of course, I mean builder, not bundler, sorry :)

Thanks, Slavek.

----- Original Message -----

...

Hi all, I just created a feature page for Rails 3.2 in Fedora 18 [1] - I figured we will need to update, as the current 3.0 is getting quite old (I'm assuming nobody is against this, right?). I'd be glad if you could give me some comments and suggestions before submitting the feature to FESCo.

Thanks.

-- Regards, Bohuslav "Slavek" Kabrda.

[1] https://fedoraproject.org/wiki/Features/Rails_3.2

-- Regards, Bohuslav "Slavek" Kabrda.

[1] https://fedoraproject.org/wiki/Features/Rails_3.2 [2] https://fedoraproject.org/wiki/Features/Rails_3.2#Scope [3] https://fedoraproject.org/wiki/Features/Rails_3.2#Dependencies _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

----- Original Message -----

On 07/10/2012 06:43 AM, Bohuslav Kabrda wrote:

...

One minor issue: rubygem-scruffy claims that it needs bundler < 3, but Rails 3.2 need bundler > 3. So it will either have to be patched (at least the gemspec) to work with new bundler or deprecated. There have been no new versions of scruffy for more than one year. Scruffy is owned by mmorsi, so Mo, could you please have a look at it?

Hey Bohuslav, sorry for the belated response, got a little behind on email.

Just updated the scruffy gem to relax the dependency from being "~> 2" to being ">= 2". The scruffy spec suite is run in the rpm and it builds fine in rawhide and on F17 so I believe we are good.

The update has been built for rawhide and has been submitted to F17 updates via bodhi.

-Mo

Hey Mo, since builder 3.0.0 is not yet in Rawhide, I bet everything works fine :) We might just want to do a scratch build when new builder lands in rawhide to see if everything works well. If not, we'll act on it then.