rubinius

[See the my email about possible views.--NO, I'm adding it below. That's the point of a ticket system--ryan]

Something thats not mentioned here is the form that the data appears

on http://ci.rubini.us. There are number of data points and vectors

within the data, so here's my idea:

• Multiple pages, showing vectors in a simple 2d table

The current page lists simple rubyspec commit, per platform. More

rubyspec commits, the page flows downward, toward older commits. This

vector shows us which rubyspecs commits are working (but not any impl.

data).

• Another page should show a snapshot view:

Impl / Last rubyspec hash / date / good:bad

This page would have a static size, defined by the number of

implementations being running against. At first, this page would just

have one row (Rubinius). This would be a heads up / dashboard page.

• Then there would be a set of pages, one per impl:

Each page would show:

rubyspec hash / date / good:bad

This page wild list all submits against the current impl, allowing

with the rubyspec hashs that were run. This page would be used to

discover when something went wrong. When either the impl. or the

rubyspecs start failing, they'll continue to fail until fixed. You can

use this page to find out where it broke, so that the breakage to be

easily found.

• Compliance page:

A single page, containing:

rubyspec hash / date / rbx / jruby / ...

This page would be used to verify over all compliance among impls.

This page is the least useful right now, with most impls having large

sections of unimplemented features. But it would have a red or green

background in each cell for each impl, depending on if it passed on

failed that rubyspec hash.

So, thats my initial breakdown of some different page views.

• Evan