The Plasma developers would like to mass-close all outdated crash reports. This has been discussed on the mailing list [1]. Please change the bugs to: status: RESOLVED resolution: UNMAINTAINED As comment for this change please use: "Thank you for this crash report and helping to improve our software. Unfortunately we were not able to work on this specific report yet. Nowadays the version this crash was reported against is no longer maintained and this makes it very difficult to work on this report as the source code might have changed and the information in the backtrace is no longer valid. Also it is quite likely that this problem got fixed in a later version. Crash reports are very often reported multiple times. If you are able to reproduce this crash with the latest version of KDE Plasma (4.10.3) please reopen this report and adjust the version information in the dropdown above and please also include a new backtrace as generated by the crash reporting tool. Please also make sure that the steps on how to reproduce the crash are precise and correct. Thank you!" The query for all bugs to include is: https://bugs.kde.org/buglist.cgi?list_id=662021&bug_severity=crash&query_format=advanced&bug_status=UNCONFIRMED&version=unspecified&version=4.5%20and%20older&version=4.6.0&version=4.6.1&version=4.6.2&version=4.6.3&version=4.6.4&version=4.6.5&version=4.7.0&version=4.7.1&version=4.7.2&version=4.7.3&version=4.7.4&version=4.8.0&version=4.8.1&version=4.8.2&version=4.8.3&version=4.9-git&version=4.7.90&version=4.7.95&version=4.8.80%20%28beta1%29&version=4.7.80&version=4.7.97&version=4.8.4&version=4.8.90%20%28beta2%29&version=4.8.95%20%28RC1%29&version=4.8.97%28RC2%29&version=4.9.0&version=4.8.5&version=4.9.1&version=4.9.2&version=4.9.3&version=4.9.80%20Beta1&version=4.9.90%20Beta2&version=4.9.95%20RC1&version=4.9.97%20RC2&version=4.9.98%20RC3&product=plasma [1] http://mail.kde.org/pipermail/plasma-devel/2013-May/025363.html
I assume that you want the bug submitter to get notified this as usual? If so, you can go ahead and use the 'mass update' function which should be shown at the bottom of the query. It will take a while as it will sent out a lot of mails, but it should work fine if you are patient. If you want them to be closed without email notifications, let us know, then we will do so.
these are about 200 bugs. I was once informed that such large numbers shouldn't be done with mass update as that can result in problems for MTAs. Is that no longer the case?
Yeah that's still the case, but it still has to be done. So if you can split it up a bit (say component 'general' vs the rest) and leave a couple hours inbetween, it should be ok.
Ok, then I will take care of it and make it in bunches of 30.