From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Council meeting 2015-04-14: call for agenda items
Date: Fri, 3 Apr 2015 16:01:32 -0400 [thread overview]
Message-ID: <CAGfcS_noUvSEcE2B9VnofS2rC0oL7WkUFk1KMYe40-_tu+trqQ@mail.gmail.com> (raw)
In-Reply-To: <mfmpto$cis$1@ger.gmane.org>
On Fri, Apr 3, 2015 at 3:33 PM, Michael Palimaka <kensington@gentoo.org> wrote:
> On 03/04/15 01:14, Tim Harder wrote:
>> The next council meeting will be on April 14th, 19:00 UTC in
>> #gentoo-council on Freenode.
>>
>> Please respond to this message on the gentoo-project list with any
>> agenda items you want to propose or discuss.
>>
>> Thanks,
>> Tim
>>
>
> Could we please revisit lagging arch teams again? Specifically, I'd like
> to see the package-by-package proposal extended to other minor archs
> including ppc and ppc64.
>
If we're going to bring this up, is sparc a concern for anybody? I
mention it only because it was brought up last time, not because I
have any specific reason to have concerns with them. If we're going
to discuss this again, we might as well be holistic.
For that matter, part of me wonders if this should really be a "minor
arch" policy vs just being general policy, and perhaps we should even
consider doing the same thing with x86/amd64. If for some reason
upstream doesn't support one of those archs or there are no major
issues with moving to the new version, why shouldn't we require arch
teams to stabilize within 90 days even for the big ones?
For reference, the policy we came up with last time for ia64 and alpha only was:
"If a maintainer has an open STABLEREQ, or a KEYWORDREQ blocking a
pending STABLEREQ, for 90 days with archs CCed and otherwise ready
to be stabilized, the maintainer can remove older stable versions of
the package at their discretion. A package is considered ready to be
stabilized if it has been in the tree for 30 days, and has no known
major flaws on arches that upstream considers supported."
The "arches that upstream considers supported" bit seems to make this
fairly suitable for anybody. The intent is to follow upstream, and if
we want to do more then that is on the arch team to make happen unless
the maintainer is willing to do it.
--
Rich
next prev parent reply other threads:[~2015-04-03 20:01 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 [this message]
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
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=CAGfcS_noUvSEcE2B9VnofS2rC0oL7WkUFk1KMYe40-_tu+trqQ@mail.gmail.com \
--to=rich@thefreemanclan.net \
--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