It's interesting that it doesn't really read fundamentally different than the release notes of the most unfashionable and enterpriesiest frameworks out there. "Enjoy the great advances of the generalized Smimgle API while ensuring to convert your Smapti configuration file. A conversion script is provided. The framework now supports Glump and Froffle including some experimental functionality that can be activated with the --zugzug flag"
Keyword was 'reads like'. Try reading it imagining you didn't know much about Rails and its terminology. You'll learn the release is a 'landmark'. And that, apparently, we now live in a world enriched by the fulfillment of the Merb Promise of 2008.
It's not a changelist, although it does link to one. "These release notes cover the major upgrades, but don’t include every little bug fix and change." It's exactly what it says, release notes. I didn't say it wasn't or that it was a product landing page. They're release notes rather reminiscent of product release notes that excitedly told you all about CORBA integration and ODBC 2 support.
I noted this as well when I upgraded my blog to Rails 3 during the bugmash last month. Rails suddenly has a lot more moving parts, and understanding the internals is much more difficult than it used to be. However as a Rails developer for almost 5 years (gosh has it been that long?) every single change adds an order of magnitude more flexibility than complexity. The surface API has grown remarkably little, but the modularity and internal API stability is dramatically improved.
The days of Rails being the scrappy upstart are over, but I think the culture and capabilities of Ruby have largely prevented the nightmarish type of scenarios that J2EE developed a reputation for. I guess it's only fair to give it another 5-10 years and see what it looks like, but developing with Rails feels just as agile as ever even if the learning curve has been steepened.
