hi, Am Mittwoch, den 06.12.2006, 12:39 +0100 schrieb Christian Kirbach: > I'd say we require some automation here. I started work on some kind of > "exact-dup-finder" that could be of use > to bugsquad and bug-buddy. Due to time and skill constraints I did no make > any progress yet. but i'm happy to read that at least somebody is looking into this. :-) > > 1) Warn the user that its software is 1 year old and should update that's http://bugzilla.gnome.org/show_bug.cgi?id=382076 , i guess. i always get that warning here (suse 10.1) and i think it's a totally stupid one, because the software i am running is NOT more than one year old. imho, this has to be checked manually on a per-app-basis and not against the gnome version, for example by manually marking application versions as "obsolete" in bugzilla.gnome.org and by checking this information (yes, i know that this is not possible yet; and no, i won't code this, i don't even know C - sorry). > > 3) Check distribution version/release; if there are updates out there > > don't allow to send if/ask for upgrade > Some list could be manually maintained and checked by bug-buddy for this > purpose. yes, also my favourite. > > 4) Same as 3, but at package level > The best way to do this is probably by using the package management system > provided by the distribution. ...which would require some interface guidelines for this. on another note, we should reject bug reports containing totally empty traces in bug-buddy already, see http://bugzilla.gnome.org/show_bug.cgi?id=383349 . let's reduce the workload as early as possible. andre -- mailto:ak-47 gmx net | failed! http://www.iomc.de
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil