[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    closing bugs products
From:       "Jordi Polo" <mumismo () gmail ! com>
Date:       2008-12-01 4:05:19
Message-ID: a4162420811302005q65fd1167uea6be1dc1d61f096 () mail ! gmail ! com
[Download RAW message or body]

There are products on bugs.kde.org that I think should be closed for new
bugs:

configure: buildsystem can be used instead. No open bugs as this writting..
binaries: downstream bugs should not be reported. No open bugs as this
writting.
daap kioslave: 1 open bug. Why not move it to kioslaves?
spreadkde.org: No open bugs. Looks unmaintained ...
printer-applet: 3 open bugs, 5 bugs reported in its life, surely should
merge with something.

There are also a bunch of applications I am not sure they are maintained
anymore (lilo-config for instance, or maybe I was don't use lilo)




-- 
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org

[Attachment #3 (text/html)]

<br>There are products on <a href="http://bugs.kde.org">bugs.kde.org</a> that I think \
should be closed for new bugs:<br><br>configure: buildsystem can be used instead. No \
open bugs as this writting..<br>binaries: downstream bugs should not be reported. No \
open bugs as this writting.<br> daap kioslave: 1 open bug. Why not move it to \
kioslaves?<br><a href="http://spreadkde.org">spreadkde.org</a>: No open bugs. Looks \
unmaintained ...<br>printer-applet: 3 open bugs, 5 bugs reported in its life, surely \
should merge with something.<br> <br>There are also a bunch of applications I am not \
sure they are maintained anymore (lilo-config for instance, or maybe I was don&#39;t \
use lilo)<br><br><br><br clear="all"><br>-- <br>Jordi Polo Carres<br>NLP laboratory - \
NAIST<br> <a href="http://www.bahasara.org">http://www.bahasara.org</a><br><br>



[prev in list] [next in list] [prev in thread] [next in thread]