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=662021&bug_severity=crash&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Clongdescs.count%2Cdupecount%2Cresolution%2Cshort_desc%2Cchangeddate&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
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
