Great, but needs one small fix
|
|
The gem compatibility should be listed by gem and ruby version. For instance, people may have reported problems on 1.9 that are fixed on 1.9.1, or between versions of gems. Maybe new gem versions will fix problems, but there will still be many failure reports listed for the old version. If everything is clumped together, it will be much more difficult to determine which gems are compatible and which are not. |
|
|
Hi, Yeah – we record the gem version for precisely that reason – we just wanted to get it released before sorting out fancy displays. We’re looking at some sort of alternative views of the collated data (by commenter, by gem version etc) but we’re not sure where we want to take it yet. Point taken about the Ruby version though. Baz |
|
|
This is the entire reason I signed up for this Beast instance… sorting through all of the reports for a gem to visually estimate which is the most reported working version is terrible. Thank god the version is reported at all though! :) I think you should display the most reported Gem and Ruby working versions together on the “short listing” (homepage). If the Gem record itself has a majority of “Working” reports on it. Not an overly difficult query to write. |