Mathew has an interesting post here about the problems with Rails 1.2, and the underlying issue of the Rails Core team not releasing software correctly.
I noticed the start of this with the 1.1.4 to 1.1.6 update (via a quick stop at 1.1.5). Looking at the change sets between the minor version changes, it was clear that we weren’t getting just a security update, but a few cool new features too. Ben and I talked about it at the time, and then Ben went on to blog about the issues
I seems that the situation hasn’t changed yet.
Apparently, DHH’s views on change are along the lines of ‘tough, this is the way I work, live with it’.
These problems haven’t affected me personally yet, but as more and more people use Rails, more will get screwed by the process and will head off back to their current platforms with tales of woe that discourage others from trying out Rails.
That would be a shame for all concerned.