On 7/2/06, Daniel Ahlberg <firstname.lastname@example.org> wrote:
> This is an automatically created email message.
> http://gentoo.tamperd.net/stable has just been updated with 15968 ebuilds.
A question  has come up on -user about why some ebuilds take so
long to become stable for an arch. This isn't the old "when will we
have KDE yesterday.3am" type question. In reviewing the above
database, and the OP, it looks like a fair number of ebuilds that
could/should be stable are not.
Of particular concern to me are packages that:
a) have no open bugs.
b) are marked stable on some archs, but not others.
c) may have only a single version available in portage.
As an example, consider net-analyzer/etherape, which is "~amd64 ppc
sparc x86", and has no open bugs (other than a version bump request),
and only a single version available in portage to begin with.
So my question is: is there anything that interested users can do to
help here? I know we can file stabilization bugs, but I agree with
Robert  that this should not be necessary in the normal case.
Besides, do you _really_ want 16,000 new bug reports that say nothing
more than "blah/foo works for me, please stabilize"! Is the problem a
lack of time, devs, arch testers, or interested users?
email@example.com mailing list