From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting
Date: Sun, 18 Sep 2011 12:14:37 -0400 [thread overview]
Message-ID: <CAGfcS_=knNjJAbNayxGbh1dXgUbEKfpk55QP=QFqJebO+Hzy2g@mail.gmail.com> (raw)
In-Reply-To: <20110918165851.020d8fb0@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Sep 18, 2011 12:05 PM, "Ciaran McCreesh" <ciaran.mccreesh@googlemail.com>
wrote:
> On Sun, 18 Sep 2011 14:20:34 +0000
> "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org> wrote:
> > As we're talking about updating profiles EAPI, what do we need to get
> > to be able to mask use flags for the stable tree, but not the testing
> > tree?
>
> Every time this has come up, the conclusion has been "it's a horrible
> idea from a QA perspective, since it would mean that testing something
> in ~arch would be different to testing it in arch".
>
Isn't that already true from a dependency standpoint? I do see your point,
but the concept of rolling out a risky flag to the brave first does make
sense.
I think the biggest issue with ~arch is when things get deployed there for a
very long time before hitting stable. That applies to libraries,
baselayout-2, or flags. Things shouldn't go to ~arch unless we have a plan
to make them stable (excepting one-offs).
Rich
[-- Attachment #2: Type: text/html, Size: 1243 bytes --]
next prev parent reply other threads:[~2011-09-18 16:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E64C7BB.907@gentoo.org>
[not found] ` <CA+Nrkpd499zUJiHee2f9wfoCgRiQCO0EXetowbPdWYmMGoaFkA@mail.gmail.com>
2011-09-07 9:07 ` [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting Tomáš Chvátal
2011-09-07 9:17 ` Andreas K. Hüttel
2011-09-07 13:21 ` Ulrich Mueller
2011-09-07 14:27 ` Tomáš Chvátal
2011-09-07 15:43 ` Michał Górny
2011-09-07 15:48 ` Michał Górny
2011-09-07 22:47 ` Aaron W. Swenson
2011-09-07 22:53 ` Ciaran McCreesh
2011-09-07 23:04 ` Brian Harring
2011-09-15 7:35 ` Michał Górny
2011-09-15 7:55 ` Ciaran McCreesh
2011-09-15 8:01 ` Michał Górny
2011-09-15 8:07 ` Ciaran McCreesh
2011-09-15 23:21 ` Arfrever Frehtes Taifersar Arahesis
2011-09-15 23:54 ` Brian Harring
2011-09-16 0:20 ` Arfrever Frehtes Taifersar Arahesis
2011-09-16 21:06 ` Zac Medico
2011-09-18 3:47 ` Donnie Berkholz
2011-09-18 5:26 ` Zac Medico
2011-09-18 6:01 ` Brian Harring
2011-09-18 6:57 ` Ulrich Mueller
2011-09-18 9:24 ` Nirbheek Chauhan
2011-09-18 9:33 ` Ciaran McCreesh
2011-09-18 14:20 ` Jorge Manuel B. S. Vicetto
2011-09-18 15:58 ` Ciaran McCreesh
2011-09-18 16:14 ` Rich Freeman [this message]
2011-09-18 17:10 ` Nirbheek Chauhan
2011-09-18 17:34 ` Zac Medico
2011-09-18 14:47 ` Michał Górny
2011-09-18 15:54 ` Ciaran McCreesh
2011-09-15 16:51 ` Brian Harring
2011-09-07 16:19 ` Ciaran McCreesh
2011-09-08 17:03 ` Thomas Sachau
2011-09-08 17:41 ` Alec Warner
2011-09-08 17:55 ` Ole Markus With
2011-09-08 18:10 ` Arfrever Frehtes Taifersar Arahesis
2011-09-08 18:35 ` Michał Górny
2011-09-08 18:33 ` Ciaran McCreesh
2011-09-08 18:43 ` Michał Górny
2011-09-09 0:45 ` Mike Frysinger
2011-09-18 11:08 ` proposal for cross-compie support in EAPI-5, was: " Thomas Sachau
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='CAGfcS_=knNjJAbNayxGbh1dXgUbEKfpk55QP=QFqJebO+Hzy2g@mail.gmail.com' \
--to=rich0@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