On 15/08/15 02:06, Simon Quigley wrote:
To whom it may concern:
Walter and I share a common concern about the packages QA tracker. It would
be great if instead of just having the results pile up(therefore eventually
making them invalid),
What makes them invalid?
If a test result for a package in week 1 of a dev cycle shows a fail and
has a bug filed against it why is that invalid in week 20 if it hasn't
been fixed?
if it would reset every so often(anywhere from 36
hours to a week would be phenomenal), then it would make those results more
useful to the QA people.
I'm not really sure how removing test results for a cycle is useful.
I would expect QA people to know if a bug reported against a package is
still relevant or not.
regards
--
Ubuntu-quality mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
