Do Ruby/Rails/whoever often have releases that break backwards compatibility?
Although sometimes it's more an issue with the documentation as opposed to code issues.
Sometimes, such changes do need to be made, though; sometimes, you have at least part of a point. On the other hand, those changes might consist of a flurry of commits every time the underlying technology's version bumps, and the project may appear dormant the rest of the time. Some might think it's a "sick" project because it only gets updates in groups every now and then, with three, six, twelve, or even eighteen months between such flurries of updates (depending on the underlying technology), but they very well might be wrong.
[Basing your impression of a given project's quality and health on project activity is dangerous.](http://blogstrapping.com/?page=2011.065.16.43.41)
Perhaps a better metric is the most recent commit combined with the number of open issues. Or maybe just the number of open issues, judged by their severity.