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

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

 



Matt Domsch (Matt_Domsch@xxxxxxxx) said: 
> > With nobody handling the incoming bugzilla tickets. With some bug
> > reports having been killed in an automated way at dist EOL. And
> > worse if it turns out that packages which do build are unmaintained
> > nevertheless, with the same symptoms in bugzilla and in package scm.
> 
> We could easily create a new class of bugzilla ticket, say
> "MAINTAINED".  An automated process would generate such tickets,
> blocking F13MAINTAINED.  The ticket would ask the maintainer to close
> the ticket to remain the owner of the package.  Tickets still open
> after $SOMEDELAY would be candidates for orphan or non-responsive
> maintainer process.  Repeat at $SOMEINTERVAL, perhaps once per release
> cycle (more would be too onerous I think).

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.

Bill
-- 
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