Re: [gentoo-dev] Gentoo ~arch testing policy?

[Bjoern Michaelsen]

On Mon, 02 Feb 2004 18:28:01 -0600
Steven Elling <ellings@×××××.com> wrote:

> How about a points rating system such as the following?
>
> Every ebuild put into the portage tree with ~ARCH gets -30 points for
> each ARCH.  For every day the ebuild is in portage, one point is added
> to the points up to a maximum of 30 points.
>
> If a user installs the ebuild and finds that it does not work, that
> user can submit a failure report to www.gentoo.org.  Upon submitting
> the failure a set amount of points are subtracted from the rating.
I like the idea. I had the same yesterday evening ;-). But I think the rating should be seperated from the ebuild - because I naively assume this to lessen the load on rsync because this frequently changing info is compiled in a seperate file in the package dir.
>
> If a user installs the ebuild and finds that it works, that user can
> submit a success report to www.gentoo.org.  Upon submitting the
> success a set amount of points are added to the rating.
I  think two ratings, one for users, one for developers without auto-incrementing would be better. User emerge failures and user emerge succeses should be affecting the user rating.
The developer rating is only modified by the devs. A dev rating below zero means it was not checked by devs (would not get into portage with the old rules), A dev rating above ten is ~arch and above 20 is arch.
A user can set thresholds for the user and the dev rating in the /etc/make.conf.
There should be a warning that it is insane and unsupported to set the dev rating threshold below ten.
The numbers are just examples but the equivalents of ~arch and arch should be well documented.
The main problem will be getting useful user feedback and preventing misuse. However it will help branches of the portage tree to develop that devs cant take constant care of (like media-radio/*).

Just my two eurocent. 


-- 
Björn Michaelsen
pub  1024D/C9E5A256 2003-01-21 Björn Michaelsen <bmichaelsen@×××.de>
   Key fingerprint = D649 8C78 1CB1 23CF 5CCF  CA1A C1B5 BBEC C9E5 A256