Le lundi 03 novembre 2008 à 11:07 -0800, Jesse Keating a écrit : > On Mon, 2008-11-03 at 19:41 +0100, Nicolas Mailhot wrote: > > The use case is checking we've actually exposed all the packages we > > intended to users. Even a mega "libs" ghetto group no one but the sanity > > checker tools parsed would get you that. > > > If the packages are in the metadata, they're exposed to the user by the > various search frontends we have to the metadata. I really really don't > understand what flooding comps will accomplish. How do you check without involving humans that every new package has been categorized (or not) as it should? It's all fine and dandy to say "some packages do not need this" but that's not a criterium automatons can verify and if it can't be auto-QAed it will rot. -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
