Hi,
On Tue, Mar 20, 2012 at 12:12:30AM -0400, Jean-François Fortin Tam wrote:
Hey all, Lately I've been studying the LAVA QA Tracker by looking at its code, setting it up on a LAVA dashboard instance in a VM and trying to use it, and asking some questions on IRC.
I recall asking at the beginning of the month if there were plans on the Linaro side to allocate developers to finish the QA Tracker in a specific timeframe, and was told that some development for this [monthly] cycle should start "next week".
However, except my own bazaar branch (crappy; it does not really solve/fix anything so far), I haven't heard of recent development activity. Or did anything happen that I missed?
Also, some people I spoke with were not aware at all of those plans for this cycle. So I'd just like to check out a few things:
- Do you have a target deadline to meet for this?
- Who are the people who will specifically be working on this?
LAVA QA tracker has been on/off the development agenda with recent activities indicating that we probably want a solution around those lines.
ATM, we are gathering requirements and decide what to do strategically on this topic. I suspect that the final input will come from the dedicated QA team that we are currently in the progress of bootstrapping.
I expect those to be the owners of requirements of such things for LAVA.
What is your interest in the QA tracker? What use-cases would you want to cover? If you want to work on this, I would suggest that we setup joint meeting with the right stakeholders to nail down what we want to do and how you can best help...