From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP concerning ebuild-development
Date: Sun, 13 Mar 2005 17:58:58 -0600 [thread overview]
Message-ID: <1110758338.9795.6.camel@pursuit> (raw)
In-Reply-To: <1110751682.9011.3.camel@nosferatu.lan>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
On Mon, 2005-03-14 at 00:08 +0200, Martin Schlemmer wrote:
> On Sun, 2005-03-13 at 15:31 -0600, Lance Albertson wrote:
> > On Sun, 2005-03-13 at 21:17 +0000, Ciaran McCreesh wrote:
> > > On Sun, 13 Mar 2005 22:05:09 +0100 Maurice van der Pot
> > > <griffon26@gentoo.org> wrote:
> > > | For instance, checking (for all arches, for all use flag combos) if
> > > | the dependencies are as stable or more stable (x86 > ~x86 > hard
> > > | masked) than the thing depending on it.
> > >
> > > Hasn't repoman been doing this correctly for a year or more now? I know
> > > it wasn't the case when I joined, but bug 24160 is long fixed...
> >
> > What if we had a service that did this check plus other stuff repoman
> > doesn't count and report it to some web site that developers can look at
> > daily to see QA bugs? Maybe run it daily or every 6-12 hours? I think
> > someone mentioned something like that once.
> >
>
> I think it would be worth a lot more if it was mailed to the maintainer
> of the ebuild (and perhaps QA?), as it takes time and effort to wade
> through a list (like the been in ~ for x days list that we used to get).
How about both options? Some people prefer getting email reports, others
prefer just going to a website. I don't see how this could be a problem,
so why not offer both? :) Perhaps we should ask the author to rewrite
his proposed GLEP to be more of a QA monitoring system that devs could
use.
Just my random thoughts...
--
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager
---
GPG Public Key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
ramereth/irc.freenode.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-13 23:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 18:49 [gentoo-dev] GLEP concerning ebuild-development Adrian Lambeck
2005-03-13 19:00 ` Ciaran McCreesh
2005-03-13 19:18 ` Martin Schlemmer
2005-03-13 19:58 ` Mark Loeser
2005-03-13 21:15 ` Sami Samhuri
2005-03-13 22:22 ` Mark Loeser
2005-03-13 20:22 ` Chris Gianelloni
2005-03-13 19:27 ` Dan Armak
2005-03-13 21:05 ` Maurice van der Pot
2005-03-13 21:17 ` Ciaran McCreesh
2005-03-13 21:31 ` Lance Albertson
2005-03-13 22:08 ` Martin Schlemmer
2005-03-13 23:58 ` Lance Albertson [this message]
2005-03-14 0:29 ` Ciaran McCreesh
2005-03-14 0:40 ` Lance Albertson
2005-03-14 0:56 ` Ciaran McCreesh
2005-03-14 0:56 ` Martin Schlemmer
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=1110758338.9795.6.camel@pursuit \
--to=ramereth@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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