public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keywording, for the umpteenth time
Date: Fri, 20 May 2005 22:22:38 +0100	[thread overview]
Message-ID: <20050520222238.157d8270@snowdrop> (raw)
In-Reply-To: <428E4DE7.70905@gentoo.org>

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

On Fri, 20 May 2005 15:51:51 -0500 Brian Jackson <iggy@gentoo.org>
wrote:
| Wouldn't it be better from a QA perspective to go back to the (really)
| old policy of dropping anything you can't test on. I know that puts
| more work on you guys, but this is only going to get worse as we get
| more devs. Wouldn't it be better to nip this in the bud now. Maybe
| broaden the arch teams by giving some devs access to remote boxes.

Not really. Dropping to ~arch when bumping works well. Sure, ~arch does
occasionally end up broken, but it's better than us lagging behind
massively. There're too many packages and not enough people these
days...

The assumption is, if foo-1.2 works on, say, sparc, then foo-1.3
probably will too to the extent that we're happy for it to go to ~sparc.
On the other hand, we're *not* confident enough in upstreams' abilities
to always put out perfect releases that we're prepared to move things to
stable without explicit testing.

See, we *really* don't want arch to get broken. We'd rather ~arch didn't
break either, of course, but taking the occasional hit there is
acceptable if it lets us keep everything up to date.

| Get every dev access to all the supported arches (some of this could
| probably be done with emulators of some sort, qemu or somesuch). Make
| them test on every arch before they change any keywords.

Not gonna happen. Emulators don't cut it and won't find all the problems
(but they will find a load of other bogus non-issues). Plus, from
experience I'd say that at least half our devs wouldn't have a clue
where to start when doing arch testing...

Then there's the issue of most alt-archs having far higher QA standards
than x86 anyway, and us not wanting to sink to what x86 considers
acceptable for marking stable.

From experience -- the current policy as it is now *works*, so long as
everyone follows it.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


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

  parent reply	other threads:[~2005-05-20 21:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 16:42 [gentoo-dev] Keywording, for the umpteenth time Jason Wever
2005-05-20 18:53 ` Duncan Coutts
2005-05-20 19:42   ` Mike Frysinger
2005-05-20 20:09   ` Jason Wever
2005-05-20 20:51     ` Brian Jackson
2005-05-20 21:18       ` Michael Cummings
2005-05-21  0:17         ` Donnie Berkholz
2005-05-20 21:22       ` Ciaran McCreesh [this message]
2005-05-20 21:49         ` Tom Wesley
2005-05-20 22:38           ` Ciaran McCreesh

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=20050520222238.157d8270@snowdrop \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@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