@Chris D help, i think someone got hacked.
Given that we see a lot of activity in the bug reports forums today with loads of bugs being closed this may indicate that we come close to a release (however not necessarily 2.4, may as well be a 2.3.14) as these kind of mass activity regarding bug reports seems typically to happen shortly before something get's released.
PS: This time they are also caring for antique bugs, loads from 2021 and this can get somewhat entertaining. I.e. someone was all of a sudden asked for clarification of the issue five years after he filed the bug report he cannot even remember after all those years while another bug that was filed for 2.2.3 back in 2021 was closed today with the hint to upgrade to 2.2.5 where that the bug would have been fixed. A bug from 2019 was closed with the note that the affected component has been rebuilt already ages ago. Another bug from 2021 was closed with the hint it would be a duplicate to a bug report from 2026 (and was fixed in 2.3.10). It seems quite clear that over five years and longer all these open bug reports have not been even looked at. Kudos to the team that they do it now and take the embarrassing route while doing so.
PS: This time they are also caring for antique bugs, loads from 2021 and this can get somewhat entertaining. I.e. someone was all of a sudden asked for clarification of the issue five years after he filed the bug report he cannot even remember after all those years while another bug that was filed for 2.2.3 back in 2021 was closed today with the hint to upgrade to 2.2.5 where that the bug would have been fixed. A bug from 2019 was closed with the note that the affected component has been rebuilt already ages ago. Another bug from 2021 was closed with the hint it would be a duplicate to a bug report from 2026 (and was fixed in 2.3.10). It seems quite clear that over five years and longer all these open bug reports have not been even looked at. Kudos to the team that they do it now and take the embarrassing route while doing so.
I think those are automated actions, maybe using AI?
Not embarrassed or an embarrassing situation n the slightest. There's quite a difference between an old bug report that has literally only ever had one person report it going unactioned for a long time versus a bug report that affects potentially millions of users. We have always prioritised those that have the biggest impact or severity.
Yes. Long term plan is to get the backlog down so it's easier to manage and surface the issues that are important that we may otherwise overlook. This adds up to more frequent maintenance releases in the long run. Using AI enables us to make quicker decisions and determine what might be the higher impact fixes.
It helps as we approach bigger release milestones too as fixes that require more extensive work may only be appropriate in a second/first point release.
I think that's due to deploying a new internal system that syncs bug complaint threads to what is actually being done behind the scenes. Unless, they just hammered everything out at once.
When It's Ready™ !
Similar threads
