Re: Orphaning Candidate packages for removal due to FTBFS, implications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Mon, 18 Jan 2010, Till Maas wrote:

> First of all, that would be two bug reports per year, as we have a 6
> month development cycle. But it also will not be that useful, as we
> already have three things that have to be done by every maintainer once
> or twice a year, so they can be easily used to track, whether or not a
> maintainer is still around at all: FAS password, Koji certificate
> Bugzilla password.
> Then if you intend to catch unused packages, this will also fail unless
> you also plan to implement some captcha for this for every package,
> because there will be a script that a maintainer can run to close all
> bugs for all of his packages at once, even for the packages he does not
> maintain properly. So you will still only track down, whether or not a
> packager is still around and not whether he cares about a certain
> package.

Yes, I believe the expression you're looking for is:

"Perfect is the enemy of the good"

What is being suggested is not perfect. It is, however, good.

-sv

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux