Package QA Tracker

[Walter Lapchynski]

so it resets every month?

@wxl | http://polka.bike
Lubuntu Release Manager & Head of QA
Ubuntu PPC Point of Contact
Ubuntu Oregon Team Leader
Ubuntu Membership Board & LoCo Council Member
Eugene Unix & GNU/Linux User Group Co-organizer
On Aug 16, 2015 12:16 AM, <flocculant at gmx.co.uk> wrote:

> On 15/08/15 16:35, Simon Quigley wrote:
>
>>
>>     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?
>>
>> My point wasn't that. Then the QA person would have to reattach the
>> bug(not so hard if there was somewhat of a history).
>>
>>     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.
>>
>> ​
>> ​Because of regression. If there is package regression and the QA tracker
>> shows a passed result, then it would be a little confusing to see a bug
>> report
>> ​ concerning the same package ​
>> by the same person, don't you think?​
>> ​
>>
> Or I would be pleased to be in a position to know that it was a regression
> because I could simply see that the same thing passed last month ;)
>
>>
>> --
>> Have a nice day,
>> Simon Quigley
>>
>
> --
> Ubuntu-quality mailing list
> Ubuntu-quality at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>