RE: [PHP-DEV] Re: [PHP-QA] RFC: A little 'howto' about bug system status's.

> >>'Duplicate' > >>The report is either bogus (e.g. empty) or send accidently > twice or more. > >>!!! Reports marked as duplicates are deleted from database from time to > >>time. !!! > > > >Ah... I have always assumed that this meant the bug was a post > about a bug > >that has already been reported. > > Maybe it really should be renamed to 'Invalid' or 'Bogus' or 'To > be killed' ?-) I treat these as bugs that are similar/the same, I normally mark the new one as duplicate and add any info to the original one. Is this wrong??? > >>'Similar to' > > Or 'Same as' or 'Related to' ? Related to is wrong as if they are the same then they should not really be there. Similar too might be somthing thats a good idea and can also be set by the original user that is reporting the new bug, IE if they have more info but are not the original reporter of the bug, we can then manually decided what to do. > >That makes sense - anyone have any issues about me adding this > (along with > >the content of this this message after everyone has had a kick > at it :) to > >the bugs page? Just tring to get youself some more work eh Zak ;) > Could you also add links to those bug reports mentioned in that > similar field..? > And the bugs mentioned in the 'similar' field should be automaticly set > to the 'similar' status and have the 'parent' mentioned in the > 'similar' field..? > Got it? =) This would be a nifty feature ;) > And you might also add 4.0.3RC2 to the version list the same time? This needs to be done.. (Wonder how many RC1's we will get rather than RC2 and how many people will ask where they can get RC2???) > Another thing would be nice also: Listing bugs by submitter.. Why is this needed??? Cheers, James