Bugs priorities

Kevin P. Fleming kpfleming at backtobasicsmgmt.com
Fri Sep 19 07:30:10 PDT 2003


Neven Has wrote:
> I have changed just a few ones.  To P1 the ones that I think should go
> into next release (1.1.8, ASAP) and to P2 the ones that have been
> mentioned a lot on mailing lists as needed, so preferably the ones
> that will be solved for the release after the next one.
> 
> 
> Neven
> 

OK, will take a look tomorrow at what can be done about them.

I think you should leave the "Version" field set to the version the 
bug was reported against, as opposed to changing it to CVS. The 
Version field should only be set to CVS when the reporter of the bug 
has duplicated the bug using the (then current) CVS HEAD code.

Who will be responsible for moving bugs from FIXED to VERIFIED and/or 
CLOSED? Do we need someone to actually download/compile/test the CVS 
code before doing that, or can we just do it when the code is 
committed to CVS?




More information about the alfs-log mailing list