From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Subject: Re: [gentoo-qa] QA checks and reports
Date: Mon, 10 Jan 2011 19:34:23 +0100 [thread overview]
Message-ID: <4D2B512F.4080809@gentoo.org> (raw)
In-Reply-To: <1294678105.2970.21.camel@saladin.home.flameeyes.eu>
On 01/10/2011 05:48 PM, Diego Elio Pettenò wrote:
> Il giorno lun, 10/01/2011 alle 16.34 +0100, Luca Barbato ha scritto:
>>
>> Some options are either received them as email or make it show up
>> through a website (like packages.g.o)
>
> One thing I'm going to make sure here is that we _will_ have a "push"
> notification; a website one has to check is _not_ going to be the only
> solution; we can add as many notifications we want but at least an email
> has to go out.
Agreed.
> I for once usually don't keep many web pages open, but I always notice
> email messages, and if we have a stable subject I'm going to put enough
> priority on those that I can receive and act on them right as they
> arrive, which is the main point of having this set up to be handled
> automatically.
I have serious problems with emails (I lose some when I get an
overwhelming number of them in a short time due thunderbird not being
able to cope with them partially)
> Besides, I sincerely don't see how fate could scale well for this kind
> of checks compared to the build checks ffmpeg runs.
The fate structure is quite sound:
- color code the situation (the bar on the top)
- group the results (per arch, we could have also per herd)
- give an aggregate view with ability to dig down
So I'd copy it.
--
Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero
next prev parent reply other threads:[~2011-01-10 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 15:34 [gentoo-qa] QA checks and reports Luca Barbato
2011-01-10 16:48 ` Diego Elio Pettenò
2011-01-10 18:34 ` Luca Barbato [this message]
2011-01-10 16:54 ` Tomáš Chvátal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D2B512F.4080809@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-qa@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox