On 26 February 2010 19:25, Kevin Kofler wrote:
[..]
> Well, as I wrote, the packager should have tested the package he's pushing
> out, of course! Especially for a new package, it's the only way to know it
> works. Something that doesn't work at all has no business being pushed to
> anywhere, even testing. And yes, checking that the dependencies are all in
> Fedora is definitely a good idea, too. (But automated depchecks would solve
> that problem once and for all.)
>

About new package point, what about the negative impact of newly
pushed package on distribution as a whole if it breaks to launch or
crashes in some event(produced in some essential functionality) and
was missed by packager/reviewer (2 people) ?

I am in favour of letting this decision made by testing team (folks
who contribute for testing in update-testing) based on package
importance and availability of contributors.

-- 
Rakesh Pandit
https://fedoraproject.org/wiki/User:Rakesh
freedom, friends, features, first
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to