Il 08/10/26 12:02, Jouni Äijälä ha scritto:
>>> I agree, old bugs should not be closed just because they are old. At
>>> the same time we should avoid this kind of situation that we have
>>> thousands of over 10 years open bugs which most likely never be
>>> fixed.

On Thu, 8 Oct 2026 at 22:37, Giuseppe D'Angelo ... replied:
>> Why not? What's the harm at keeping them open?
>> I think this is the fundamental question that hasn't been answered.

Jason McDonald (9 October 2026 02:17) added:
> Indeed. Anyone who doesn't want to see old bugs can easily set Jira to
> filter them out by creation date, length of inactivity or Version
> Found. That's better than unilaterally hiding them from everyone.

In particular, TQtC's needs could be adequately met by adding a tag (I
think "not_in_TQtC_scope" would be more apt than the one currently used)
to the tickets currently being closed and adding a check for that to the
filters through which TQtC views bug lists without these tickets.

...
>>> Reason why we are not using "need more info" yet is that by doing
>>> this we would kind of ask people to retest every bug and this is not
>>> what we want.

>> *The Qt project* ought to retest them.
>> The reporter has already done their job.

> Agreed. I suspect that a significant percentage of those bugs could be
> automatically retested using AI and/or that AI could be used to fill
> in missing info (such as minimal test cases) that could improve the
> chance of a developer choosing to work on them. Perhaps such an
> exercise would make for a good intern project.

That seems eminently credible - it could, indeed, be a background task
to scan everything with the TQtC-specific "not in scope" tag and remove
it if able to reproduce in a recent version, adding that version to the
"Affects Version" list.  I've manually done such a verification for one
ticket that had a clear test-case attached and saved a few more to do
manually as a background task, but it's a task ideally suited to
automation.

        Eddy.
-- 
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development

Reply via email to