Re: Re: PHP 4.0 Bug #6984 Updated: problems w/ session_destroy() function

At 11:46 PM 10/2/00 +0200, André Langhorst wrote:

(I just got 1 feedback of 4 requests for same bug from different submitters) And that 'similar' or 'same as' status could work like this: When one of the bug reports is closed then ALL of the submitters of the bugs mentioned in similar bugs field receive that closing notice..

that´s right, as far as we´ve got some invalid state it´ll be fine to provide such kind of support

agreed

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???

If I´m able to reproduce I do the same. If not I´ve added "this bug is a duplicate of #9xxxx" to the "main" report and vice versa Summary of most important tasks: 1) Differentiate "Duplicate" to "Duplicate" (meaning similar information) and "Invalid" (meaning bogus and invalid bugs, and they should not be deleted, but disregarded in bugdb queries and so on, to give php-doc a hint about common pitfalls) 2) All bugs need an additional field "duplicate of" to easily mark bugs as a duplicate (side effects similar to bugzilla) 3) We need a "status whiteboard" or "keywords" field to be able to mark some bugs as "QA 4.0.3" to force fixing specific bugs.

I am not sure that I understand exactly what you mean - perhaps I should rephrase it as I understand it: Provide a field that indicates that this bug must be fixed before the specified version of PHP can be released.

I don´t want to be responsible for grey hair on zaks head :) so that´s all

Thanks for your work André (Yes, I still have all the old discussions - as soon as Sterling (hopefully :) and myself get some time, we will get back at the bug reporting system. I am still free from gray hair. Well, at least on my head - I have started getting one or two in my beard... - zak