Only support modern rubies

[jacobo]

how about it?

[coveralls]

Coverage remained the same when pulling d6c978c on engineyard:modern_ruby into 543fbec on resque:master.

[steveklabnik]

I am tempted to say this is acceptable for 2.0, as long as we provide bug backports for 1.x. I'm going to post to the mailing list to see what people think.

[ekampp]

I agree with @steveklabnik that it would be fine for the next, major version (2.0).

In general, if it becomes a burning platform, at some point, you need to cut support. And cutting that with the next major version fits with the semver scheme.

[steveklabnik]

Straight from the horse's mouth: https://twitter.com/steveklabnik/status/350521242081697792

I'm going to merge this for now, since it's been a few days and nobody has raised any significant issues. However, until the actual release, I consider this an open discussion topic. I'm fine with doing this as long as we continue to provide bugfixes for 1-x-stable for the people who are still stuck on 1.8.