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

List:       kopete-devel
Subject:    Re: [Kopete-devel] BKO status
From:       Jeff Stuart <jstuart () computer-city ! net>
Date:       2004-02-17 5:32:01
Message-ID: 200402170032.02133.jstuart () computer-city ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 12 February 2004 01:52 pm, Jeff Stuart wrote:
> Since I am unable at this time to do any major coding, I will use my time
> to go through the bugs that have been reported for kopete and try to verify
> that they all exist.  I will also check for dup bugs, etc.  FYI, at this
> time, I see there are 83 bugs open for kopete (not including wishlists).
>
> --
> Jeff Stuart
> jstuart@computer-city.net

Ok, I have gone through all of the currently open bugs.  At this time, we have 
a total of 51 open bugs.  Now, I was thinking that as things continue, to 
check all of the unconfirmed bugs about once every week or two to see what 
the status is.  And if after a few "What's the status of this" (say 2 or 3) 
if it's still unconfirmed AND we have NOT heard back from the original 
reporter of the bug to close it as an invalid bug. 

Also, every other week or once a month if every other week is too much to go 
through the new and assigned bugs checking on status.  This way, the original 
reporter of the bug (and any one else who's keeping an eye on it) won't feel 
ignored on.  IE this is just a communications thing back to the original 
reporter.  

Over the next couple of days (3-7), I'll be going over the wish lists, 
checking to see if any are truely bugs, and also for dup wishes.

If any of the above is a problem, PLEASE let me know. :)

Oh, also.  I'm assuming that if a dev says "Ok, I'll go check this out and see 
how I can fix it" then the bug is actually a confirmed bug and then I change 
it's status to NEW.

[Attachment #5 (application/pgp-signature)]

_______________________________________________
Kopete-devel mailing list
Kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel


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