I completely agree with this. We (bugsnag) are running on rails 4 beta right now to help iron out any production issues before that is released.

We didn't, however, realize that "patch" releases also have release candidates. I'd recommend following the rails blog (http://weblog.rubyonrails.org/) which announces release candidate builds too.

Thanks for the blog post - and I didn't realize that patch releases also had RC.

It looks like this release was quite fat, for a patch release.

I added "check rails diff" to my deploy todo list.

EDIT: I just noticed that http://weblog.rubyonrails.org/ doesn't have a way to subscribe by email. I signed-up by email with this site instead http://blogtrottr.com, in case it helps other here.

You can also subscribe to the rails-core mailing list, all betas, RC and full releases get announced there.

There's quite a bit more discussions on rails-core apart from RC and releases, so subscribing to the blog is a good idea if your time is limited :-)

Ok, yes, that's an extremely great and open-source way to handle this.

But seriously, can we at least expect moderately stable releases? I do not think that's too much to ask, especially for a framework which has, in the past, achieved that.