Mass closing EOL bugs should not close bugs with pending updates

[Christoph Wickert]

Am Montag, den 18.02.2013, 07:12 -0500 schrieb Jaroslav Reznik:
> ----- Original Message -----
> > Am Sonntag, den 17.02.2013, 14:46 +0100 schrieb Tadej Janež:
> > > On Sun, 2013-02-17 at 12:02 +0100, Christoph Wickert wrote:
> > > > 
> > > > I found that a couple of F16 bugs were closed by endoflife at fp.o
> > > > even
> > > > though there were pending updates for F17 and F18 to fix them. As
> > > > a
> > > > result, the bugs are now closed WONTFIX even they were or are
> > > > going to
> > > > be fixed.
> > > 
> > > What you describe is another example of strange behavior of the
> > > Fedora
> > > EOL Closure script.
> > > I discovered two related problems that I described three days ago:
> > > http://lists.fedoraproject.org/pipermail/devel/2013-February/178649.html
> > > 
> > > Since then I found a page that describes the Fedora 16 EOL Closure
> > > procedure:
> > > https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora18#Fedora_16_EOL_Closure
> > > 
> > > It says that the bugs with "version == Fedora 16" and "status !=
> > > CLOSED"
> > > are subject to automatic closure. Could you give an example of a
> > > bug
> > > that you described?
> > 
> > https://admin.fedoraproject.org/updates/FEDORA-2013-2359/lxpanel-0.5.12-1.fc18
> > and
> > https://admin.fedoraproject.org/updates/FEDORA-2013-2359/lxpanel-0.5.12-1.fc17
> > fix several bugs, among them two very old and annoying ones:
> > https://bugzilla.redhat.com/show_bug.cgi?id=782431 and
> > https://bugzilla.redhat.com/show_bug.cgi?id=785906
> > 
> > As you can see the bugs were already ON_QA before they were closed
> > WONTFIX.
> 
> But for F16 - it's true - the fix is not going to be available in F16,
> thus WONTFIX.

I disagree. We have CURRENTRELEASE and NEXTRELEASE and they are exactly
for this purpose. A bug appeared in an older version, it was filed
against this version and as the bug affects that version, it should
remain assigned to it. If it however gets fixed later, we should let our
users know, thus we have the update fix that bug, so there is a link in
bugzilla and the resolution becomes CURRENTRELEASE or NEXTRELEASE.

>  Correct resolution is to bump version to F17/F18 or clone bugs.

Despite of the question whether it's right or wrong it's a manual
process and we cannot rely it really happens. On the other hand changing
the script to not close any bugs which are ON_QA is easy.

So what is so bad about ignoring bugs MODIFIED and/or ON_QA bugs?

Kind regards,
Christoph