On Tuesday 30 June 2009, Dirk Mueller wrote: > I don't see the reason for coming up with a solution before the problem is > understood. I've not seen any bugreports against RC1 that are confusion. > which ones? bugnubmers, query, examples please?
https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=4.3+rc1&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bug 198315 in that list were good and useful, the others less so. i think bug 198279 would have been filed regardless, the rest shouldn't have been. basically, when going through these reports i can't rely on the "4.3 rc1" tag meaning much of anything right now. which is a shame since we generally know which bugs we've fixed prior and post various pre-releases, and seeing them pop up again (eroniously) is concerning and causes time spent investigating non-issues. it could be avoided with a higher degree of coordination between upstream KDE, downstream packagers and the users of those packages. it's not the end of the world, but it was a surprise. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
