intertwingly

Yehuda Katz: ... have focused quite a bit on maintaining backward compatibility (for the user-facing API) with Rails 2.3. If you try edge and find that we’ve broken something, definitely let us know.

I’ve been running automated tests on Rails, focusing on edge, for nearly a month now.  Four problems were found during the process:

• ticket 2779 was probably found before I could even report it, in any case it was quickly fixed.
• ticket 2731 could theoretically have gone unnoticed during development, but certainly would have been found and fixed before release.
• ticket 2734 is the only one that might have been more difficult to debug later; or to put it another way, knowing exactly what change broke this function make debugging easier.
• ticket 2759 was the only one that had any realistic possibility of escaping into the wild — and that one was specific to 2.3 and did not affect Rails edge.

If this trend continues — and I see no reason to believe otherwise — upgrading a deployed application to 3.0 (a major release) will prove to be easier than upgrading to a “dot” release (e.g. 2.3) was in the past.