Hi,
----- Original Message -----
From: "Tim Flink" tflink@redhat.com
<snipped> Do we have any documentation on what ResultsDB is supposed to do other than store and display test results?
I've found several wiki pages about ResultsDB ([1], [2], [3]) and some old emails ([4], [5]) but I have yet to find any references to ResultsDB being used inside AutoQA tests for anything other than reporting.
Granted, it isn't a stretch to see ResultsDB used that way but I dislike making assumptions about what a given feature is going to do - it leads to "feature XXX is a magical cure-all that will solve all of our problems if we could only get it implemented" types of thinking.
<snipped>
I'm currently working on a ResultsDB resumé https://fedoraproject.org/wiki/User:Jskladan/Sandbox:ResultsDB_Writeup (work in progress though). Storing results is probably the least important role for ResultsDB. The main purpose of resultsdb is to provide data source for various 'frontends' via easy-to-use querying API. So this is the reason why we want to wait for ResultsDB. Once we have the data in, we can wery easily make a frontend, which will present 'Subset of updates which can be pushed now' to Rel-Eng. We'll take the latests Depcheck result, check whether some of the updates changed (which would discard either the respective update or the whole result as such).