From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Council meeting 2015-04-14: call for agenda items
Date: Tue, 07 Apr 2015 19:25:07 -0400 [thread overview]
Message-ID: <55246753.5060902@gentoo.org> (raw)
In-Reply-To: <mg0tli$cq1$1@ger.gmane.org>
On 04/07/15 11:38, Michael Palimaka wrote:
> On 07/04/15 08:22, Matt Turner wrote:
>> On Mon, Apr 6, 2015 at 1:52 PM, Pacho Ramos <pacho@gentoo.org> wrote:
>>> For instance, in this topic I haven't seen any comment from
>>> alpha/ia64/sparc arch teams...
>> I haven't commented because I don't honestly believe people care.
>>
>> I'm really disappointed that the discussion is entirely about creating
>> keyword-dropping policies and no one is asking whether there are
>> things we can do to make keyword/stable requests a more streamlined
>> process. But, that kind of thing seems to be par for the course on
>> this list.
> We've heard very little from arch teams at all, let alone proposals for
> improving the stabilisation process. That's the main reason this sort of
> topic keeps coming up.
>
>
I don't want my silence to be misinterpreted regarding ppc and ppc64.
For those arches, I'm willing to trim back on stabilization, but I
really don't want to drop to ~ as we did for mips. In fact, I'm
thinking of turning mips itself back into a stable arches with just the
@system packages being candidates for stabilization. The reason I like
this approach is when I build stage3's I can control what I know will
build (stable packages) vs the latest packages added to the tree
(~arch). Nothing is more painful than have to manually intervene in a
bunch of catalyst builds. Being able to control what will be built via
stable keywords saves time and effort.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2015-04-07 23:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 14:14 [gentoo-project] Council meeting 2015-04-14: call for agenda items Tim Harder
2015-04-02 16:45 ` Ulrich Mueller
2015-04-03 19:33 ` [gentoo-project] " Michael Palimaka
2015-04-03 20:01 ` Rich Freeman
2015-04-03 20:13 ` Andreas K. Huettel
2015-04-04 14:31 ` Michael Palimaka
2015-04-04 15:13 ` Rich Freeman
2015-04-04 15:44 ` Michał Górny
2015-04-04 15:48 ` Michał Górny
2015-04-04 22:02 ` William Hubbs
2015-04-05 12:32 ` Pacho Ramos
2015-04-05 12:44 ` Ben de Groot
2015-04-05 19:50 ` William Hubbs
2015-04-05 20:20 ` James Le Cuirot
2015-04-05 21:27 ` Andrew Savchenko
2015-04-05 22:54 ` Rich Freeman
2015-04-05 23:05 ` Patrick Lauer
2015-04-06 0:47 ` Rich Freeman
2015-04-06 7:55 ` Michał Górny
2015-04-06 20:52 ` Pacho Ramos
2015-04-06 22:22 ` Matt Turner
2015-04-07 15:38 ` Michael Palimaka
2015-04-07 23:25 ` Anthony G. Basile [this message]
2015-04-07 23:29 ` Rich Freeman
2015-04-07 23:50 ` Anthony G. Basile
2015-04-08 11:51 ` William Hubbs
2015-04-08 13:33 ` Rich Freeman
2015-04-08 17:39 ` William Hubbs
2015-04-08 18:15 ` Rich Freeman
2015-04-08 22:41 ` William Hubbs
2015-04-09 0:01 ` Rich Freeman
2015-04-08 11:58 ` Michael Palimaka
2015-04-07 23:38 ` Rich Freeman
2015-04-07 23:42 ` Francesco Riosa
2015-04-08 0:01 ` Matt Turner
2015-04-08 0:35 ` Rich Freeman
2015-04-05 23:38 ` Andrew Savchenko
2015-04-06 7:59 ` Michał Górny
2015-04-06 10:29 ` Rich Freeman
2015-04-06 11:09 ` Michał Górny
2015-04-06 21:37 ` Andrew Savchenko
2015-04-06 22:05 ` Michał Górny
2015-04-06 22:25 ` Andrew Savchenko
2015-04-06 22:28 ` William Hubbs
2015-04-07 0:02 ` Rich Freeman
2015-04-06 9:28 ` [gentoo-project] " Michał Górny
2015-04-11 7:13 ` Ben de Groot
2015-04-11 9:04 ` Ulrich Mueller
2015-04-11 11:58 ` Rich Freeman
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=55246753.5060902@gentoo.org \
--to=blueness@gentoo.org \
--cc=gentoo-project@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