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

List:       kde-devel
Subject:    Re: The number of unassigned bugs is worrisome
From:       "Mark A. Taff" <marktaff () comcast ! net>
Date:       2006-01-11 22:33:38
Message-ID: 200601111433.38124.marktaff () comcast ! net
[Download RAW message or body]

On Wednesday 11 January 2006 14:19, David Faure wrote:
> On Wednesday 11 January 2006 23:16, Mark A. Taff wrote:
> > What has to happen for a bug to be confirmed?  I just checked on a _very_
> > old bug (http://bugs.kde.org/show_bug.cgi?id=37520) I commented on and it
> > is still unconfirmed.  I can confirm it on every version of KDE from at
> > least 3.3.2 to 3.5.0.
>
> ?? That's not a bug, that's a wishlist.
> I don't even have time to read most wishlists.

I stand corrected about its current official status being "wishlist", but my 
real question was about what has to happen to make a reported bug or wish 
into a confirmed bug or wish.

I couldn't find any howto or overview at bugs.kde.org dealing with how bugs 
get confirmed.

IMO this bug is mis-filed as a wishlist, as KDE _tries_ to mount the device 
and fails as opposed to not trying at all.  Should I file a new bug report?

Regards,

Mark
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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