On Wed, Nov 04, 2026 at 10:44:21AM +0000, Jouni Äijälä via Development wrote: > Hi David, > > Thanks for sharing this. We will try this at some point how this works. > Especially regarding bugs reported closer to a supported Qt version,
I don't think that proximity to a supported Qt version plays a big role here. Especially in mature areas that do not see much churn the age of an issue is unlikely to correlate strongly with its validity. > see this as being even more fruitful. it may help us identify bugs that > should remain open. Identifying bugs that should remain open can be done by re-triaging against supported versions of Qt. From personal experience, that's a job AI is pretty good at, including creating reproducers in case the issues are still there. Regards, Andre' PS: Whether it's worthwhile to fix every open issue, or whether one can argue that certain kinds of mis-behaviour would rather hurt existing applications, and it'd be better to keep the existing, unplanned state, is an independent discussion, that should be handled case-by-case. And also there, documenting the formerly unexpected but now expected behavior would be the prefered action. -- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
