4 ms·

Having played this game repeatedly, I suggest waiting until 4.1 or so. Point releases are often buggier than intended, such is life, and it's going to take anot

by phillmv 13y ago

Having played this game repeatedly, I suggest waiting until 4.1 or so. Point releases are often buggier than intended, such is life, and it's going to take another year before plugins start requiring it anyways. If you're on 2.3.x upgrade, otherwise wait a bit.

look_lookatme 13y ago
I think Rails 4.1 is when all current deprecations are being removed, which is going to be a bit hairy for people accustom to <= Rail 3.x finder syntax and ancient plugins that somehow manage to still work. To the OP, I suggest you launch with 3.x and upgrade immediately after to 4 and start taking note of deprecations.
- phillmv 13y ago
  >which is going to be a bit hairy for people accustom to <= Rail 3.x finder syntax and ancient plugins that somehow manage to still work. Yeah, but that pain will come regardless. Better I think to wait until the dust settles on turbolinks et al and plugin authors update. You could always update first to 4.0.x (for mild to large values of x) or what have you before jumping over to 4.1. Point is, if you've got a large app it's not worth pushing back any deadlines. Someone's gotta do it! and much to love to the rails-core team, but being 3 months behind the release schedule still counts as "bleeding edge" in most of the rest of the software world ;).
- jpdoctor 13y ago
  > To the OP, I suggest you launch with 3.x and upgrade immediately after to 4 and start taking note of deprecations. I think this is the most likely outcome. Thanks again to everyone for the discussion too.
- rhizome 13y ago
  Last time we went through this, I wrote one app in 3.0, got a sense of the deprecations, started another at 3.1, then did straight 2>3 updates or new apps in 3.2 once I had it all down. There's no hurry.
steveklabnik 13y ago
> it's going to take another year before plugins start requiring it anyways. If anyone has gems that don't work with 4 yet, please let me know. Most of them at least have a branch going, but I'm always curious, and am willing to help out to upgrade things.

by phillmv 13y ago

look_lookatme 13y ago

I think Rails 4.1 is when all current deprecations are being removed, which is going to be a bit hairy for people accustom to <= Rail 3.x finder syntax and ancient plugins that somehow manage to still work. To the OP, I suggest you launch with 3.x and upgrade immediately after to 4 and start taking note of deprecations.

phillmv 13y ago
>which is going to be a bit hairy for people accustom to <= Rail 3.x finder syntax and ancient plugins that somehow manage to still work. Yeah, but that pain will come regardless. Better I think to wait until the dust settles on turbolinks et al and plugin authors update. You could always update first to 4.0.x (for mild to large values of x) or what have you before jumping over to 4.1. Point is, if you've got a large app it's not worth pushing back any deadlines. Someone's gotta do it! and much to love to the rails-core team, but being 3 months behind the release schedule still counts as "bleeding edge" in most of the rest of the software world ;).
jpdoctor 13y ago
> To the OP, I suggest you launch with 3.x and upgrade immediately after to 4 and start taking note of deprecations. I think this is the most likely outcome. Thanks again to everyone for the discussion too.
rhizome 13y ago
Last time we went through this, I wrote one app in 3.0, got a sense of the deprecations, started another at 3.1, then did straight 2>3 updates or new apps in 3.2 once I had it all down. There's no hurry.

steveklabnik 13y ago

> it's going to take another year before plugins start requiring it anyways. If anyone has gems that don't work with 4 yet, please let me know. Most of them at least have a branch going, but I'm always curious, and am willing to help out to upgrade things.