Nightly stability chart (user editable)

[jrabbit]

A demo: ​http://serenity.jrfxmedia.com:8080/ Source: ​https://github.com/jrabbit/are-we-stable-yet

Most of the work is done in Python. I used the Bottle framework, jQuery UI and Fabric. This was my first time using Bottle and Fabric.

Bonus features:

HTTP GET'ing ​http://serenity.jrfxmedia.com:8080/working/r4000 will set the revision to a "working" state. ​http://serenity.jrfxmedia.com:8080/nightlies exposes a json dict of the database.

[jrabbit]

This chart tracks [the last user] report of stability on a given Haiku revision. This is mostly to track known "unstable" or "bad" builds so that users can find stable nightlies and so the Haiku team can see trends in stability. It would be fairly trivial to add graphing for this purpose. Multiple "votes" on stability could be counted but until a problem emerges good/bad is enough for now.

[humdinger]

I like the idea! How about having optional comments for every entry? People could add what exactly is unstable. It may be just one component, like recently the synaptics touchpad acting up. For people on desktops with a normal mouse, the release may have been perfectly stable. One could add a link to the respective ticket in trac.
I'd also prefer a vertical list instead of a horizontal scroller with big buttons.

[jrabbit]

A vertical list could be done as a preference. I don't want to encourage what should be a trac ticket as a comment, so maybe it can only allow a trac link with the title displayed.

I'll probably start the the alternate view since that can be done in pure python, then look at the extended reporting.

[jrabbit]

Ok it now has a table view, accepts trac tickets, and even validates the trac tickets.

​https://github.com/jrabbit/are-we-stable-yet/commits/master

[nielx]

Closing due to the age of the ticket.