Auto-expiring bugs are getting absurd

[Jaroslav Reznik]

----- Original Message -----
> On Fri, Feb 07, 2014 at 01:33:31AM -0800, Adam Williamson wrote:
> > There is a kind of magic trick for this: if you set a bug to be against
> > Rawhide and give it the FutureFeature keyword (which is our 'official
> > way' of identifying RFEs), it won't ever be re-based to a stable release
> > at Branch time, and hence won't ever get EOLed. That's a bit secret
> > sauce-y, though.
> 
> Huh, cool. *goes off to add that to a bunch of open bugs against my
> packages*.

Rule
---
All must be met

    version == rawhide
    component != "Package Review"
    opened against rawhide before 2013-08-20 (Rawhide Branching date is 2013-08-20)
    keyword FutureFeature is not present
    keyword Tracking is not present
    the string RFE is not present in the summary
    status != CLOSED 

Please look also for not properly set up tracker bugs (missing Tracking keyword)
 and future features (RFE or FutureFeature keyword) bugs. 
---

That last sentence is also what I try to do - at least the first part, I'm 
grepping bug list for tracker/future feature/RFE and I'm always trying to reach
maintainers before doing any action.

Jaroslav

> --
> Matthew Miller    --   Fedora Project    --    <mattdm at fedoraproject.org>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct