public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: About reducing or even removing stable tree for some arches
Date: Wed, 18 Feb 2015 10:25:07 +0100	[thread overview]
Message-ID: <1424251507.27408.122.camel@gentoo.org> (raw)
In-Reply-To: <pan$1982$dba205be$9d9c0d7$86a72918@cox.net>

El mié, 18-02-2015 a las 03:11 +0000, Duncan escribió:
> Pacho Ramos posted on Mon, 16 Feb 2015 14:34:50 +0100 as excerpted:
> 
> > 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.
> 
> Perhaps my non-dev status prevents me from understanding the difficulty 
> here, but...  I really don't see the problem.

Maybe that explains it, I have personally suffered it when we needed to
dekeyword most gnome stuff on all arches but amd64/x86 and even months
later we were still needing to remember to either keep moving to testing
other packages or finally postponing the move to testing for some and
try to stabilize some again (as the chain of reverse dep kept growing
forever).

I don't want to have to repeat that for every package that is not
attended in 90 days, and seeing that the arch teams that are unable to
stabilize/keyword things are, consequently, also unable to make this
huge work, the 90 days policy isn't going to start working any time soon
(it has never worked indeed as nobody wants to do the manual job of
checking all the reverse deps, move that deps to testing, recheck for
the reverse deps of those, and repeat and repeat).




      reply	other threads:[~2015-02-18  9:25 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
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 [this message]

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=1424251507.27408.122.camel@gentoo.org \
    --to=pacho@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