Re: Assigning keyword/stable bugs to arch teams (WAS: [gentoo-dev] dropping redundant stable keywords)

[Pacho Ramos <pacho@gentoo.org>]

El dom, 16-02-2014 a las 09:03 -0500, Rich Freeman escribió:
> On Sun, Feb 16, 2014 at 3:41 AM, Pacho Ramos <pacho@gentoo.org> wrote:
> > Also, keeping the bugs assigned to package maintainers will still allow
> > them to try to get that pending bugs fixed (or resolved in some way) as
> > they will take care more about that specific package status. If we get
> > that bugs assigned to arch teams, they will likely be ignored by both
> > parts, getting worse.
> 
> Well, that depends on your perspective.  If they fix them by deleting
> the old version, then whether they've made things better or worse is a
> matter of philosophy.

I think that, if they delete del old version without breaking the tree
(and, then, moving the package to testing for that arch), the situation
is improved. But, if the bug is assigned to the same team that cannot
handle its stabilization, I doubt they will move it to testing either.

> 
> That's basically the counter-argument to removing old versions.  If
> the newer version doesn't work at all, then the old buggy version is
> superior.  It is better to have the bugs ignored, than to pester the
> maintainer until the package is disabled entirely.

But, I guess there are two major cases:
- Versions that cannot be stabilized due they not working on that arch
any longer
- Versions that are not stabilized because arch team doesn't have the
man power to do that.

I am referring to the second case that is also really common. This also
raises again the question about being enough to do build tests for that
arches or not. If that is the case, would be nice if maintainers could
have access to that machines to let us help them :) (if I would build
them on that arches, I would try to help for sure)