Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
Given the increasing size of the portage tree I'm becoming concerned
about the rate at which ebuilds move from the unstable ~arch keyword to
the stable one.
Has a formalized process been discussed for this? The first thing that
comes to mind is a set of tinderboxes designed to build packages with
predictable flags sending reports to each ebuild maintainer.
The second is more practical and within reach; advocacy of
stable.gentoo.org, and a policy of accepting a package as stable when
five or more users have vouched for it and two weeks have passed without
a bug report.
These are rough ideas, I'd love to hear some input on them. Any
thoughts?
--
// -- http://www.BRAD-X.com/ -- //
--
gentoo-dev@g.o mailing list
|
|
