On Sun, 16 Feb 2014 08:23:27 +0100
Tom Wijsman <[email protected]> wrote:
> > > While it was not explained here, the idea can also move the actual
> > > maintenance of the ebuild to the arch team; such that it becomes
> > > the arch team's responsibility to deal with it, or rather don't
> > > deal with it
> >
> > How would that ever work?
>
> The responsibility is moved away from the maintainer; and thus also
> its bugs, as well as the need to rely on a newer version to become
> stable.
The (slightly rhetorical) question was how an understaffed team could
be realistically expected to start maintaining ebuilds. Your entire
reply missed that point.
The answer to the question is that you can't. A package maintainer
cannot burden an understaffed team with more work. They are
understaffed, so they will not do the work, and the maintainer has an
itch to scratch (stop maintaining an older version of a package).
Now guess who will be actually doing the work.
jer