Jani Taskinen writes:
> On Sun, 11 Mar 2001, Stanislav Malyshev wrote:
>
> >JT>> Uhm..I have always closed the duplicates after the original (which they
> >JT>> refer to) was closed. Any opinions about this? As the current bug system
> >
> >I thought "Duplicate" itself is a closed status. Like, work continues on
> >the original and the duplicate is officialy dead from now, nobody tocuhes
> >it anymore.
>
> If that bug system was smart enough, it would close childs too when the
> parent is closed. But it isn't. So you should always close also the
> duplicates when the original is fixed. This way the ones who submitted
> the duplicates know also that it's fixed.
>
> Bogus == Dead. :)
>
> --Jani
Now, it's Sunday morning, I just crawled out of my nice warm bed, and
I haven't finished my first cup of bad coffee yet--but if
Duplicate == Repeated information, and
Repeated Information == Useless Bug Report, and
Useless Bug Report == Bogus,
does not, therefore:
Duplicate == Bogus?
And both Duplicate and Bogus mean that the bug report is dead and
shouldn't be touched (I tend to agree with Stas on this one):
Just wondering...and this is just an addled early-morning
thought...what would be the downside of have a very simple Open/Closed
flag field for each report, along with a status modifier field of
Duplicate, Analyzed, Bogus, etc.
--
+----------------------------------------------------------------+
|Torben Wilson <[EMAIL PROTECTED]> Adcore Finland|
|http://www.coastnet.com/~torben http://www.adcore.com|
|Ph: 1.604.709.0506 [EMAIL PROTECTED]|
+----------------------------------------------------------------+
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
