Hello

With last gnome maintained packages stabilization round I noticed some
pending stabilizations/keywordings for really a long time waiting for
ppc* teams. For example:
https://bugs.gentoo.org/show_bug.cgi?id=470768 -> it's waiting for more
than a year and it's blocking from dropping old versions for so long
https://bugs.gentoo.org/show_bug.cgi?id=508006 -> the same case, and we
cannot drop that stable keywords because looks like ppc team still wants
to keep kde in stable

Then, I finally needed to ask Agostino for help because of that and I
wondered if there are some kind of issue in this teams, if they are
still able to keep ppc* as stable arches or... :/

I see two options:
- Move ppc* to testing only -> I guess some people will disagree as this
architecture is not so old and probably it's still used by enough people
- Clarify what packages do they really want in stable. 

The problem of all this is that, as it is shown in this concrete
example, if they want to keep, for example, KDE in stable, they will
need to also be fast enough for other dependencies. If not, we could go
with the "package-per-package" proposal that was approved one year ago
by the Council for alpha/ia64. 

But the problem of "package-per-package" proposal is shown in:
https://bugs.gentoo.org/show_bug.cgi?id=470768#c9

Once we start dropping stable keyword in one package, we need to do the
same in reverse-deps, that will also have other reverse-deps... and that
it ends up being a lot of work arch teams cannot accomplish (as they are
the same teams that are so overloaded that cannot keep stabilizing fast
enough) and things get blocked forever :(

That is the reason for me thinking that maybe the way to go would be to
do the opposite -> keep only base-system and a few others stable and
drop stable for most of the rest. This big effort could be accomplished
in a week by other developers willing to help (like me) and would solve
the issue for the long term. I guess that is what HPPA team did in the
past and I think it's working pretty well for them (in summary, have a
stable tree they are able to keep stable). That will also help people in
ppc* teams to know that the remaining stabilization bugs, apart of being
much less, are important enough to deserve rapid attention, as opposed
to current situation that will have some important bugs mixed with tons
of stabilization requests of apps that got ppc stable keywords years ago
and are currently no so important.

Thanks a lot


Reply via email to