On 15 May 2010 21:07, Till Maas wrote: > On Sat, May 15, 2010 at 10:19:50AM -0500, Matt Domsch wrote: >> On Tue, May 11, 2010 at 01:26:53PM -0800, Jeff Spaleta wrote: >> > What we have is the orphaning (a proactive process) and awol >> > maintainer processes (a reactive process).. we don't have an automated >> > process that helps us identify potentially unmaintained packages to be >> > concerned about. >> >> Well, we do have two more: fever which sends emails when packages have >> newer upstream releases, and my own FTBFS runs (which I stopped for >> F13 after it branched; I'll restart that for rawhide when F13 is >> released). > > The upstream release monitoring tool (formerly fever) is not really used > to identify such packages, because there is no process to identify > non-uptodate packages like there is a process to identify old FTBS-bugs. > Yes, and I think it is time to draft a proposal for same. Remember Seth also had a script (which he ran quite recently to figure our concerned packages). -- Rakesh Pandit https://fedoraproject.org/wiki/User:Rakesh freedom, friends, features, first -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
