Re: [RFC] Closing outdated crash reports
Am 2013-05-25 14:34, schrieb Aaron J. Seigo: On Saturday, May 25, 2013 09:19:19 Martin Graesslin wrote: Plasma has many open crash reports for outdated versions [1]. I would suggest to close them all as: +1 from me. Sysadmin request created: https://bugs.kde.org/show_bug.cgi?id=320343 Cheers Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
[RFC] Closing outdated crash reports
Hi all, Plasma has many open crash reports for outdated versions [1]. I would suggest to close them all as: a) Stack traces most likely do not match any more b) It's quite likely that it's a duplicate c) Users can easily reopen if it's still valid with latest version d) If it's a crash and still valid it will be reported again (given enough eyes...) I would suggest the following template for closing (native speakers: please correct): 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! As new status I would suggest RESOLVED/UNMAINTAINED. Comments? Cheers Martin [1] https://bugs.kde.org/buglist.cgi?list_id=661950bug_severity=crashquery_format=advancedbug_status=UNCONFIRMEDbug_status=CONFIRMEDbug_status=ASSIGNEDbug_status=REOPENEDversion=unspecifiedversion=4.5%20and%20olderversion=4.6.0version=4.6.1version=4.6.2version=4.6.3version=4.6.4version=4.6.5version=4.7.0version=4.7.1version=4.7.2version=4.7.3version=4.7.4version=4.8.0version=4.8.1version=4.8.2version=4.8.3version=4.9-gitversion=4.7.90version=4.7.95version=4.8.80%20%28beta1%29version=4.7.80version=4.7.97version=4.8.4version=4.8.90%20%28beta2%29version=4.8.95%20%28RC1%29version=4.8.97%28RC2%29version=4.9.0version=4.8.5version=4.9.1version=4.9.2version=4.9.3version=4.9.80%20Beta1version=4.9.90%20Beta2version=4.9.95%20RC1version=4.9.97%20RC2version=4.9.98%20RC3product=plasma ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [RFC] Closing outdated crash reports
On 2013年05月25日 15:19, Martin Graesslin wrote: Hi all, Plasma has many open crash reports for outdated versions [1]. I would suggest to close them all as: a) Stack traces most likely do not match any more b) It's quite likely that it's a duplicate c) Users can easily reopen if it's still valid with latest version d) If it's a crash and still valid it will be reported again (given enough eyes...) I like the idea in general, but the suggested bug list is a little dangerous (meaning it might cause very bad public image) : 1. it contains quite a few CONFIRMED and REOPENED reports, so closing them will certainly make users angry and be reopened again later. For such reports, we could ask can someone try and see whether it is still valid in 4.10.3 ? but really should not close it and wait for angry users to shout and reopen it. 2. it contains quite a few reports with high amount of comments or duplicates. Again, bad candidates for closing. I would suggest using this bug list[1] as the base. [1] https://bugs.kde.org/buglist.cgi?list_id=662021bug_severity=crashcolumnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Clongdescs.count%2Cdupecount%2Cresolution%2Cshort_desc%2Cchangeddatequery_format=advancedbug_status=UNCONFIRMEDversion=unspecifiedversion=4.5%20and%20olderversion=4.6.0version=4.6.1version=4.6.2version=4.6.3version=4.6.4version=4.6.5version=4.7.0version=4.7.1version=4.7.2version=4.7.3version=4.7.4version=4.8.0version=4.8.1version=4.8.2version=4.8.3version=4.9-gitversion=4.7.90version=4.7.95version=4.8.80%20%28beta1%29version=4.7.80version=4.7.97version=4.8.4version=4.8.90%20%28beta2%29version=4.8.95%20%28RC1%29version=4.8.97%28RC2%29version=4.9.0version=4.8.5version=4.9.1version=4.9.2version=4.9.3version=4.9.80%20Beta1version=4.9.90%20Beta2version=4.9.95%20RC1version=4.9.97%20RC2version=4.9.98%20RC3product=plasma ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [RFC] Closing outdated crash reports
On Saturday 25 May 2013 17:40:10 Jekyll Wu wrote: On 2013年05月25日 15:19, Martin Graesslin wrote: Hi all, Plasma has many open crash reports for outdated versions [1]. I would suggest to close them all as: a) Stack traces most likely do not match any more b) It's quite likely that it's a duplicate c) Users can easily reopen if it's still valid with latest version d) If it's a crash and still valid it will be reported again (given enough eyes...) I like the idea in general, but the suggested bug list is a little dangerous (meaning it might cause very bad public image) : 1. it contains quite a few CONFIRMED and REOPENED reports, so closing them will certainly make users angry and be reopened again later. For such reports, we could ask can someone try and see whether it is still valid in 4.10.3 ? but really should not close it and wait for angry users to shout and reopen it. oh that was just an example query. I would have tried to get it more fine- grained. I think your one looks really good, but I will probably also have a look at the CONFIRMED and REOPENED ones - personal experience: it doesn't mean anything, especially REOPENED. Cheers Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [RFC] Closing outdated crash reports
On Sat, May 25, 2013 at 12:06 PM, Martin Graesslin mgraess...@kde.orgwrote: 1. it contains quite a few CONFIRMED and REOPENED reports, so closing them will certainly make users angry and be reopened again later. For such reports, we could ask can someone try and see whether it is still valid in 4.10.3 ? but really should not close it and wait for angry users to shout and reopen it. oh that was just an example query. I would have tried to get it more fine- grained. I think your one looks really good, but I will probably also have a look at the CONFIRMED and REOPENED ones - personal experience: it doesn't mean anything, especially REOPENED. reopened on a very old bug often means a similar issue that the reporter may think is the same, but often ends up completely unrelated ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [RFC] Closing outdated crash reports
On Saturday, May 25, 2013 09:19:19 Martin Graesslin wrote: Plasma has many open crash reports for outdated versions [1]. I would suggest to close them all as: +1 from me. -- Aaron J. Seigo signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
