public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ppc@gentoo.org, ppc64@gentoo.org, alpha@gentoo.org,
	sparc@gentoo.org, ia64 <ia64@gentoo.org>
Subject: Re: [gentoo-dev] About reducing or even removing stable tree for some arches
Date: Mon, 16 Feb 2015 10:37:12 -0600	[thread overview]
Message-ID: <20150216163712.GA1506@linux1> (raw)
In-Reply-To: <1424093690.27408.35.camel@gentoo.org>

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

On Mon, Feb 16, 2015 at 02:34:50PM +0100, Pacho Ramos wrote:
> Hello
> 
> Every day I am hitting tons of blockers stabilizations and keywording
> requests for alpha, sparc, ia64, ppc and ppc64. 
> 
> Again, I would suggest to either decrease radically the amount of stable
> packages of some of that arches or even make them testing only.
> 
> For reducing their stable tree, my suggestion would be to either keep
> their current stage3 packages stable or stage3+some concrete (and
> public) list of packages.
> 
> Currently situation is not good at all as we rely on mostly one member
> needing to handle most stable work and, if any stablereq has any issue
> leading to it not being able to be handled in an "automated" way, the
> bug gets blocked for months. Also, keywording work is mostly stalled on
> this arches as it's done by even less people.
> 
> The current policy of maintainers dropping keywords after 90 days is
> simply not applied because it leads up to that maintainer needing to
> kill himself that keyword and ALL the reverse deps keywords and, then,
> all that effort should probably be replaced by making the opposite, I
> mean, reducing the stable tree of that arches to a minimum and moving
> all the other packages to testing. The main advantage of this is that it
> needs maybe more effort in one round but it solves the problem for the
> future. On the other hand trying to kill keywords of a package *and all
> its reverse deps* requires a lot of work every time the problem appears.

I think the cleanest way forward would be to mark these arch's dev or
exp in the profiles. That way, maintainers don't have to worry about
them and the people maintaining the arch's can determine what needs to
be stabilized at their own paces.

William


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

  parent reply	other threads:[~2015-02-16 23:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 13:34 [gentoo-dev] About reducing or even removing stable tree for some arches Pacho Ramos
2015-02-16 15:09 ` Rich Freeman
2015-02-16 15:16   ` Pacho Ramos
2015-02-16 15:36 ` Anthony G. Basile
2015-02-16 15:59   ` Joshua Kinard
2015-02-16 23:28     ` Rich Freeman
2015-02-20  8:06     ` Christopher Head
2015-02-16 16:05   ` Pacho Ramos
2015-02-16 21:22     ` Anthony G. Basile
2015-02-16 22:45       ` Mike Gilbert
2015-02-16 16:37 ` William Hubbs [this message]
2015-02-17  4:49   ` Michał Górny
2015-02-16 22:47 ` William Hubbs
2015-02-18  3:11 ` [gentoo-dev] " Duncan
2015-02-18  9:25   ` Pacho Ramos

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=20150216163712.GA1506@linux1 \
    --to=williamh@gentoo.org \
    --cc=alpha@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ia64@gentoo.org \
    --cc=ppc64@gentoo.org \
    --cc=ppc@gentoo.org \
    --cc=sparc@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