public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Wed, 9 Mar 2005 18:42:42 -0500	[thread overview]
Message-ID: <20050309234242.GB15846@time.flatmonk.org> (raw)
In-Reply-To: <422F7F4B.4090406@gentoo.org>

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

Alin Nastac wrote:	[Wed Mar 09 2005, 05:57:15PM EST]
> No gentooer 
> expects from a ~arch ebuild to be stable, so the sky would not fall if 
> you made a mistake and release it under this keyword. When I hear "I 
> cannot mark foo library as ~arch because I don't know how to test it" 
> smells like excuse to me.

Earlier you said that you mark ebuilds stable after 30 days with no
bugs.  Now you're suggesting that marking ~arch by mistake isn't a big
deal.  I don't wish to beat up on you further, but this viewpoint can
lead to stable ebuilds in the tree that don't even build over the
course of one month (other than February ;-)

> As for QA... does anyone think we *can* have proper QA procedures,
> with our release speed and decentralized development model? And with
> only ...  350 devs from which God knows how many are still active?
> :-D Who thinks that clearly doesn't have a clue what QA means. It is
> practically impossible to test every combination of
> ebuilds/USE/CFLAGS so all we do is a surface test, letting the
> burden of testing on the shoulders of our users.

You're right, we don't have real QA yet.  But it's still better to try
the best we can rather than marking things blindly on the basis that
"we don't have QA anyway"

Regards,
Aron

--
Aron Griffis
Gentoo Linux Developer


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-09 23:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09  2:00 ` Hasan Khalil
2005-03-09  7:38 ` Alin Nastac
2005-03-09 13:39   ` Stephen P. Becker
2005-03-09 14:50     ` Alin Nastac
2005-03-09 16:22       ` Ciaran McCreesh
2005-03-09 17:38         ` Alin Nastac
2005-03-09 18:38           ` Ciaran McCreesh
2005-03-09 18:56             ` Alin Nastac
2005-03-09 19:10               ` Stefan Schweizer
2005-03-09 19:10                 ` Stefan Schweizer
2005-03-09 21:30                 ` Luis F. Araujo
2005-03-09 22:57                 ` Alin Nastac
2005-03-09 23:27                   ` Stephen P. Becker
2005-03-10  0:50                     ` Donnie Berkholz
2005-03-10  0:18                       ` Daniel Goller
2005-03-09 23:36                   ` Jason Wever
2005-03-09 23:42                   ` Aron Griffis [this message]
2005-03-10  7:54                     ` Alin Nastac
2005-03-10  8:27                       ` Ciaran McCreesh
2005-03-10 15:54                         ` Chris Gianelloni
2005-03-10 15:52                       ` Chris Gianelloni
2005-03-10  4:34                   ` Grant Goodyear
2005-03-10  8:36                     ` Alin Nastac
2005-03-10 13:14                       ` Ciaran McCreesh
2005-03-10 16:00                       ` Chris Gianelloni
2005-03-10 19:00                         ` Alin Nastac
2005-03-10 19:33                           ` Chris Gianelloni
2005-03-10 21:25                             ` John Myers
2005-03-10 15:38                   ` Chris Gianelloni
2005-03-09 19:18               ` Patrick Lauer
2005-03-09 19:43                 ` Stefan Schweizer
2005-03-09 19:56                   ` Patrick Lauer
2005-03-10  0:55               ` Jon Portnoy
2005-03-10  8:07                 ` Alin Nastac
2005-03-09 19:20             ` Chris Gianelloni
2005-03-09 16:37       ` Stephen P. Becker
2005-03-09 16:43   ` Chris Gianelloni
2005-03-09 17:40     ` Alin Nastac

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=20050309234242.GB15846@time.flatmonk.org \
    --to=agriffis@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