[dboyd]

Rails 4.0.0 was released 129 days earlier, on June 25...

  http://weblog.rubyonrails.org/2013/6/25/Rails-4-0-final/

I'm very impressed with Rails 4, not just the overall level of improvements, but also the stability of what was released. To go more than 4 months without a patch is especially impressive for something like Rails.

[dominotw]

To be fair non obvious bugs come from being used in production apps. And 4 months is not enough time for those bugs to surface.

[steveklabnik]

Basecamp in particular is usually running on near-edge Rails, so we have at least one big production app to find out things.

"Agile Web Development with Rails" also does CI against edge edge Rails, so that's being checked at all times too.

I'm not going to say there's a ton of production apps using latest, but there are some, at least.

[VeejayRampay]

The release cycle seems to be extremely clean these days, thanks and congratulations to you all.

[steveklabnik]

Thanks. Decisions were recently made to specifically make it easier to upgrade, even when it's worse for us: I removed a feature that we later reverted, for example. So it's nice to hear that it's appreciated. <3

[danso]

I've dabbled with toy apps in 4 and have been very impressed with how smooth the change has been from 3 to 4. I haven't tried directly migrating a Rails 3 app so far (as 3.2.15 has been holding up quite well) but would anticipate it being far less of a hassle than moving from 2 to 3. AFAIK, Github is still on Rails 2

[Axsuul]

Upgraded a pretty big Rails app from 3 to 4 a month ago, only took an afternoon.

[kingnothing]

Github is basically on their own branch of rails at this point. They use the 2.x base, but have pulled in pieces and parts of subsequent releases.