Bugs priorities

Kevin P. Fleming kpfleming at backtobasicsmgmt.com
Fri Sep 19 09:39:49 PDT 2003

Neven Has wrote:

> Then they should all be set to CVS. :)  These are all "initial" bugs
> from my todo lists and all apply to the latest version, now in CVS.  I
> just don't want to change the version of each one alone, and spam the
> list again just for that, so I'm simply changing it when I do
> something else with a bug.

OK, makes sense.

> Well, instead of what I did for bug 619, maybe I should have just
> marked the bug as VERIFIED, after checking your patch.  Then you, or
> somebody else would commit it to CVS and at that point CLOSE it?
> And if you can, you can close that bug now. :)

Done. I think that the plan should be the bug assignee posts their 
patch to resolve the bug and changes the status to FIXED, someone else 
does a code review/etc. and changes the status to VERIFIED, and then 
either the bug assignee or the reviewer does the CVS commit and 
changes status to CLOSED.

I haven't heard back yet on getting belgarath accounts/CVS access for 
Vassili and myself yet, so as it stands today Neven is only one that 
can do the CVS commit/change to CLOSED step. But any of us should be 
able to do code review/change to VERIFIED.

More information about the alfs-log mailing list