Hi Rui, On Sat, Oct 1, 2011 at 23:20, Rui Maciel <rui.mac...@gmail.com> wrote: > On 09/30/2011 03:03 PM, Myriam Schweingruber wrote: >> >> Well yes, it is feasible, provided the database is completely triaged >> and there are actual people doing the queries, as those need to be >> done by sentient beings. Of course we welcome all volunteer triagers >> to give a hand:) See also my previous post though. > > What do you mean by "completely triaged"? If I'm not mistaken, by default > KDE's bug tracker lists bug reports sorted by report ID, which is directly > proportional to how old a bug report is and therefore "how long they have > been unanswered". This means that if you run a search on KDE's bug tracker > for the bugs filed on a specific project, the first result that pops out by > default is already the report which has been left unaddressed the longest. > > > Rui Maciel
The age of a bug doesn't tell anything about its importance. Especially regressions, which are more important due to there nature are usually much younger than old reports. Many old reports are also completely outdated, as they don't apply to the most recent version. One of the task of the bug triager is also to go over all older reports and check with the reporter if it is still valid in the most recent released version, or ideally in the git version. FWIW: most of those request from the triagers are simply ignored as we only rarely get feedback on those, another time waster in triaging. As a general rule, bug reports to the KDE bugtracker should always be only about the latest released version or the currently developed one, we don't do backports, that is up to the distributions to do so. Again, a matter of manpower. I just think that all the time we now have invested in this thread could have been better spent by everybody in bug triaging and/or coding, don't you all think the same? Regards, Myriam -- Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
