Drop support for Rails 2? #728

Closed
jyurek opened this Issue Feb 3, 2012 · 6 comments

Projects

None yet

5 participants

Member
jyurek commented Feb 3, 2012

We've discussed this before and said we'd only support the latest 2 versions of Rails. Since we have Rails 3.2, 3.1, and 3.0, and 3.0 has been out for a while now, we should revisit the idea of dropping Rails 2 support.

Owner

What kind of code could we remove by dropping Rails 2 support? What sort of additional features could we add by only supporting 3.1 and 3.2?

Owner

Supporting only Rails 3 means we only support Ruby 1.9, right?

Can we work this into dropping support for WIndows somehow?

Member
jyurek commented Feb 3, 2012

I don't think we can drop support for Windows. A number of people use it there, and, in fact, one of the highest trafficked tickets here was one where installation failed for Windows users.

We'd still need to support 1.8.7, because Rails still supports it. When we go to Rails 4-only, we can drop 1.8 support.

@joshuaclayton, There is some configuration that we do that's different based on Rails version that we can get rid of, and we can make sure we're using the latest hooks into Rails itself.

Contributor
sikachu commented Feb 3, 2012

Paperclip 3.0 should target only Rails 3.0.x and up. People with Rails 2.x can use version ~> 2.5

Contributor

I know this is already happening, but we can make the tests about 3x faster, which will improve the project all around.

Contributor
sikachu commented Apr 4, 2012

Oh, this is done!

@sikachu sikachu closed this Apr 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment