Orphaning Candidate packages for removal due to FTBFS, implications
Tomas Mraz
tmraz at redhat.com
Mon Jan 18 19:01:23 UTC 2010
On Mon, 2010-01-18 at 12:25 -0500, Seth Vidal wrote:
>
> On Mon, 18 Jan 2010, Bill Nottingham wrote:
>
> > Ugh, this seems like it would just create a lot of make-work for the
> > common case where packages *are* maintained. Perhaps only do this
> > for packages that appear via some criteria (have not been built, have
> > not been committed to, have lots of bugs with no response, etc.), but
> > doing it for *every* package seems like overkill.
> >
>
> Right - so maybe last check into devel branch since the last release of
> the distro.
>
> If we do that check before the alpha release that should let us track down
> awol maintainers and unmaintained pkgs pretty easily, I think.
>
> thoughts?
I think there should be at least two conditions which would have to be
fulfilled for the nagging bug to be created - the package was not
touched by the maintainer during recent x months and at least one bug is
opened not closed in the bugzilla on the package.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
More information about the devel
mailing list