[gentoo-qa] QA checks and reports

[gentoo-qa] QA checks and reports

[Luca Barbato]

Referring http://bugs.gentoo.org/show_bug.cgi?id=351239

Seems we could have some nice automated reports thanks to pkgcore, one
of the items undecided is how to report the results.

Some options are either received them as email or make it show up
through a website (like packages.g.o)

Surely I'd love to have a way to have a easy way to know how we are (see
fate.lscube.org for an example) in a webpage.

lu

-- 

Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero

Re: [gentoo-qa] QA checks and reports

[Diego Elio Pettenò]

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

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.

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.

Besides, I sincerely don't see how fate could scale well for this kind
of checks compared to the build checks ffmpeg runs.

-- 
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-qa] QA checks and reports

[Luca Barbato]

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

Re: [gentoo-qa] QA checks and reports

[Tomáš Chvátal]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 10.1.2011 16:34, Luca Barbato napsal(a):
> Referring http://bugs.gentoo.org/show_bug.cgi?id=351239
> 
> Seems we could have some nice automated reports thanks to pkgcore, one
> of the items undecided is how to report the results.
> 
> Some options are either received them as email or make it show up
> through a website (like packages.g.o)
> 
> Surely I'd love to have a way to have a easy way to know how we are (see
> fate.lscube.org for an example) in a webpage.
> 
> lu
> 
I am all hands for the website. Cause it allows even non-maintainers to
see and fix issues (provide patches/etc) which allows better community
blending :)

And people LOVE colourfull stuff :P
http://dev.gentooexperimental.org/~scarabeus/reports/xorg-todo.html

Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0rOeMACgkQHB6c3gNBRYfm4QCgnBGleI8JQnhfHcos0BZBON1r
Wj0AoIG1ZCkZXJwfRWTNuCpxogHzZ+7e
=9zLs
-----END PGP SIGNATURE-----