On Wed, Aug 19, 2015 at 4:18 AM, Pasi Lallinaho
wrote:
> On 19/08/15 09:27, floccul...@gmx.co.uk wrote:
> > On 18/08/15 21:44, Nicholas Skaggs wrote:
> >> It can be setup anyway you wish. Historically it's been found useful
> >> to retain the results for an entire cycle at once for packages. When
On 19/08/15 09:27, floccul...@gmx.co.uk wrote:
> On 18/08/15 21:44, Nicholas Skaggs wrote:
>> It can be setup anyway you wish. Historically it's been found useful
>> to retain the results for an entire cycle at once for packages. When
>> we removed older results, we got duplicate bugs and it was ha
On 18/08/15 21:44, Nicholas Skaggs wrote:
It can be setup anyway you wish. Historically it's been found useful
to retain the results for an entire cycle at once for packages. When
we removed older results, we got duplicate bugs and it was harder to
see what had been touched and what had not. It
I guess it would be great if the Package QA Tracker worked like this in my
opinion.
People can submit QA results like usual. Every 24 hours minimum(when all
the results are submitted for each individual set, passed or failed, like
for Lubuntu Desktop, Ubuntu GNOME, etc) the QA tracker could go
It can be setup anyway you wish. Historically it's been found useful to
retain the results for an entire cycle at once for packages. When we
removed older results, we got duplicate bugs and it was harder to see what
had been touched and what had not. It would be interesting to have a
discussion abo
I'm all ears, Nick!
@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 9:44 AM, wrote:
> On 16/08/15 17:27, Walter Lapchy
On 16/08/15 17:27, Walter Lapchynski wrote:
so it resets every month?
No.
It doesn't reset at all. Just finishes at cycle end and then starts again.
Nick can tell you more about why it was set up as it is.
@wxl | http://polka.bike
Lubuntu Release Manager & Head of QA
Ubuntu PPC Point of Co
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, wrote:
> On 15/08/15 16:35, Simon
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
>
> 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 r
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
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), if it would reset every so often(anywhere from 36
hours to a week would be phenomenal), then it woul
12 matches
Mail list logo
