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. 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. We will use "need more info" later on once we get closer to supported Qt versions. So by default closing the bugs now with "won't do" does not mean that they are not valid bugs. We kind of accept quality debt and then who disagrees that can update the bugs with supported Qt version and they will remain open. Also the same for already closed bugs by reopening them. These particular bugs have now better chance to get fixed. Also we are not deleting the bugs from database. They can still be found by the label "not in maintenance scope" even if they are closed.
Thanks for the constructive comments. Lots of compromises need to be made in this exercise ;) -Jouni ________________________________ From: Giuseppe D'Angelo Sent: Wednesday, October 07, 2026 15.59 To: [email protected] Subject: Re: [Development] Error database cleaning continues Il 25/09/26 10:45, Giuseppe D'Angelo via Development ha scritto: > I must say I'm not pleased at all with this process. From the > notifications I'm getting, a ton of widgets-related bugs are being > closed "simply" because they're old. Also, why are the bugs closed with "Won't do"? That's a quite wrong resolution. It should be "Needs more info" (= we don't know if they are still valid, please verify and reopen) or a similar status. "Won't do" means we will NOT accept a bugfix for them, as we consider the behavior described in the report the intended one. Thanks, -- Giuseppe D'Angelo | [email protected] | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - Trusted Software Excellence Confidential
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
