unassigned bugs (Re: Closing all bugs?)

Jonathan Jesse jjesse at gmail.com
Tue Dec 18 15:22:46 GMT 2007


On Dec 18, 2007 6:24 AM, Lubos Lunak <l.lunak at suse.cz> wrote:

> On Tuesday 18 of December 2007, David Faure wrote:
> > On Tuesday 18 December 2007, Matthias Kretz wrote:
> > > On Tuesday 18 December 2007, David Faure wrote:
> > > > If you know of any other component assigned to null at kde.org, please
> > > > tell me or reassign it to unassigned-bugs at kde.org.
> > >
> > > Most of KView is assigned to null at kde.org.
> >
> > Hmm, but in this case the final component is correct, we don't need to
> > reassign it.... so should I really change KView to make bugs go to
> > unassigned-bugs at kde.org?
>
>  If the theory is that unassigned-bugs should also allow seeing somebody
> adding a patch and reacting on it, then yes. However, if KView is dead,
> will
> be dead, and nobody cares about it *shrug*.
>
> --
> Lubos Lunak
> KDE developer
> --------------------------------------------------------------
> SUSE LINUX, s.r.o.   e-mail: l.lunak at suse.cz , l.lunak at kde.org
> Lihovarska 1060/12   tel: +420 284 028 972
> 190 00 Prague 9      fax: +420 284 028 951
> Czech Republic       http//www.suse.cz
>

Pretty much a lurker/newbie here to KDE-Devel but is there a how-to guide on
triaging bugs?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071218/e38d98bb/attachment.htm>


More information about the kde-core-devel mailing list