@steveklabnik says it's time: https://twitter.com/steveklabnik/status/215520849447501826
Upgrading only makes sense if you gain something you need, or are forced to in order to maintain. We use a variety of tools designed to keep you at an older version until that time comes. In my opinion, upgrade when you have to, never earlier!
Basically, explain why.
Disregarding neat features in 3.2.x, no bugs are getting fixed in the 3.1 series. How much that matters is up for debate.
@steveklabnik Are there any bugs in 3.1 that are actually affecting us?
I'd rather see current bugs fixed in our existing code than worrying about upgrading to a new version of rails when it really doesn't matter at this point.
I haven't actually used rstat.us in any way in a really long time, so I have no idea. If Carol hadn't @replied me on the ticket, I probably wouldn't even be in here.
Faster dev mode has been a really nice feature in other apps.
It's the security fixes I'm most concerned about.
But 3.1 is still getting those security fixes.
Right, but since we're still on 3.1.6, we have like 6 gaping security holes due to old rails... so at least we should upgrade to the newest 3.1.x.
And I just upgraded that too, for values of just==10 days ago :( 401fc95
hmmm it looks like 3.1.6 is the latest 3.1.x??? https://rubygems.org/gems/rails/versions
Yeah, I'm dumb. It's 3.0.15.
Ok I found another reason to upgrade... draper only supports rails 3.2 as of 0.13.0 and i want the minitest integration in draper 0.15.0 :(
I can backport you a fix to the 0.12.x branch for the short term.
Meh. I think I have us upgraded to rails 3.2.8; it wasn't too bad. Got us off of a github version of omniauth in the process. I think it's time.
Upgrade rails, coffee-rails, sass-rails and sass. Fixes issue #545.