Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Rails 4.2 #1102

Closed
jywarren opened this issue Dec 14, 2016 · 7 comments
Closed

Upgrade to Rails 4.2 #1102

jywarren opened this issue Dec 14, 2016 · 7 comments
Labels
help wanted requires help by anyone willing to contribute

Comments

@jywarren
Copy link
Member

We're starting to get warnings for the paperclip gem:

DEPRECATION WARNING: [paperclip] [deprecation] Rails 3.2 and 4.1 are unsupported as of Rails 5 release. Please upgrade to Rails 4.2 before upgrading paperclip. (calle
d from <class:Image> at /home/warren/sites/plots2/app/models/image.rb:12)
DEPRECATION WARNING: [paperclip] [deprecation] Rails 3.2 and 4.1 are unsupported as of Rails 5 release. Please upgrade to Rails 4.2 before upgrading paperclip. (calle
d from <class:User> at /home/warren/sites/plots2/app/models/user.rb:21)

Worth trying it out in the Gemfile and Gemfile.lock and seeing how the tests do?

@jywarren jywarren added the help wanted requires help by anyone willing to contribute label Dec 14, 2016
@mridulnagpal
Copy link
Member

@jywarren I'd like to try it out

@jywarren
Copy link
Member Author

jywarren commented Dec 14, 2016 via email

@mridulnagpal
Copy link
Member

@jywarren So what all things will I have to do? I don't know where to start

@jywarren
Copy link
Member Author

Yeah it's a tough one. I think for starters, change the gemfile and run 'bundle install' and then add the Gemfile.lock -- then create a PR. We'll see what happens.

I ran a search for "Rails 3" and "Rails 4" and didn't find anything. So I guess we see what happens?

It looks like the big one is from Rails 3-4, here: http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0

And then from 4.0-4.1 is not as bad, as can be expected. I'm not sure, but it looks like we'll want to go to 4.2!

@pycarlson
Copy link
Contributor

@jywarren and @mridulnagpal I would like to help with this one. I've done an upgrade in the past so let me know if you want my help.

@mridulnagpal
Copy link
Member

mridulnagpal commented Dec 20, 2016 via email

@jywarren
Copy link
Member Author

jywarren commented Apr 5, 2017

Merge into #1318 --

@jywarren jywarren closed this as completed Apr 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted requires help by anyone willing to contribute
Projects
None yet
Development

No branches or pull requests

3 participants