From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PcLKt-0003ZD-6g for garchives@archives.gentoo.org; Mon, 10 Jan 2011 17:15:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B68DDE0740 for ; Mon, 10 Jan 2011 17:15:14 +0000 (UTC) Received: from mail-ww0-f41.google.com (mail-ww0-f41.google.com [74.125.82.41]) by pigeon.gentoo.org (Postfix) with ESMTP id 23A2DE05A5 for ; Mon, 10 Jan 2011 16:52:52 +0000 (UTC) Received: by wwi18 with SMTP id 18so1787930wwi.4 for ; Mon, 10 Jan 2011 08:52:48 -0800 (PST) Received: by 10.227.72.203 with SMTP id n11mr2959921wbj.93.1294678100072; Mon, 10 Jan 2011 08:48:20 -0800 (PST) Received: from [172.28.64.58] (host249-252-static.95-94-b.business.telecomitalia.it [94.95.252.249]) by mx.google.com with ESMTPS id 11sm20204224wbj.13.2011.01.10.08.48.18 (version=SSLv3 cipher=RC4-MD5); Mon, 10 Jan 2011 08:48:19 -0800 (PST) Sender: =?UTF-8?Q?Diego_Elio_Petten=C3=B2?= Subject: Re: [gentoo-qa] QA checks and reports From: Diego Elio =?ISO-8859-1?Q?Petten=F2?= To: gentoo-qa@lists.gentoo.org In-Reply-To: <4D2B26FD.9080402@gentoo.org> References: <4D2B26FD.9080402@gentoo.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-KwSG8BzBLuFMpHItIv6m" Date: Mon, 10 Jan 2011 17:48:25 +0100 Message-ID: <1294678105.2970.21.camel@saladin.home.flameeyes.eu> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-qa@lists.gentoo.org Reply-to: gentoo-qa@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 X-Archives-Salt: ef457e07-9206-4981-94e7-23bf5257979a X-Archives-Hash: 24ea012e877bb940f5893c7829988292 --=-KwSG8BzBLuFMpHItIv6m Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Il giorno lun, 10/01/2011 alle 16.34 +0100, Luca Barbato ha scritto: >=20 > Some options are either received them as email or make it show up > through a website (like packages.g.o)=20 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. --=20 Diego Elio Petten=C3=B2 =E2=80=94 Flameeyes http://blog.flameeyes.eu/ --=-KwSG8BzBLuFMpHItIv6m Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iQEcBAABAgAGBQJNKzhWAAoJEBqCrVe7WSRDeZMH/RfYBKsjlf2pPaYM+ug5Jepe 145PriIRmoo+300GDqzXwaTYAJir99tH6BUtsQft2q412kM1ny6euKk/mVZcsXLS y1Frnfpg270sqwsMF5+t8xLB7Ft95qIdPCRxMOoVqgTuValrRTFt7Qcc9CIJkfFn m2crL2Nsu9KX2i77Fj4vU37dq5jfjvXk+VfK2tJeQwT5oV2nSxIlYlv4p0Rbzc23 21Wzqa/58NT+nR69fXSeXmglkXkcCyrTKpIypzG+S5+wq8t9X06wkzHCu7LsJMZ8 lQjBE0+ZjC+9/WKrVr3SuuRsvkC+n2px/ou98KUtoa0EgykZC1L6ZHb77OjX0SQ= =sCyN -----END PGP SIGNATURE----- --=-KwSG8BzBLuFMpHItIv6m--