Edit report at https://bugs.php.net/bug.php?id=77452&edit=1

 ID:                 77452
 Updated by:         c...@php.net
 Reported by:        chealer at gmail dot com
 Summary:            Issue tracker: Undefined status "Wont fix"
 Status:             Closed
 Type:               Feature/Change Request
 Package:            Website problem
 PHP Version:        Irrelevant
 Assigned To:        petk
 Block user comment: N
 Private report:     N

 New Comment:

Thanks for the pointer!  Now fixed as
<https://github.com/php/web-bugs/commit/4025362c44a6407f17bf84ea17dc044c9416d97d>.


Previous Comments:
------------------------------------------------------------------------
[2022-01-07 00:45:07] chealer at gmail dot com

Thank you Tiffany, but what do you mean by "closing a bug"?

------------------------------------------------------------------------
[2021-07-25 16:50:32] tiff...@php.net

> can you clarify what "the closing comment" refers to?

When a bug is closed as "wont fix" a comment by the person closing the bug is 
submitted explaining why the bug was closed. Hence, it's a "closing comment."

------------------------------------------------------------------------
[2021-07-25 16:41:56] chealer at gmail dot com

Thank you Peter, but your addition starts with a closing LI tag, rather than an 
opening one, causing the HTML to be invalid and the item to display as part of 
the previous one.

Also, can you clarify what "the closing comment" refers to?

------------------------------------------------------------------------
[2019-05-04 11:45:47] p...@php.net

Automatic comment on behalf of peterko...@gmail.com
Revision: 
http://git.php.net/?p=web/bugs.git;a=commit;h=98337280da29ac042159c2280895d0b4ec753a01
Log: Fix #77452: Undefined status Wont fix

------------------------------------------------------------------------
[2019-01-27 15:50:04] chealer at gmail dot com

c...@php.net wrote:
> > Undefined status "Wont fix"
>
> I do not really understand this request.  “Wont fix” means “won't
> fix”, and that means that the PHP developers won't fix an issue
> (even though it is acknowlegded as such), for reasons to be stated
> in the closing comment.

What do you mean by closing comment? In any case, I have seen that status used 
on mere RFE-s (not bugs), so if that's the intended usage, there should 
probably be a note about the real-world usage too. I don't see how a developer 
could predict with certitude that a certain issue will not be fixed though.

[...]

> > some statuses are also probably not needed anymore and are left
> > from the past...
>
> From what I can tell, all statuses still are needed (maybe
> “critical” should be a separate field, though).

I probably agree that "Critical" should not be a status; I filed ticket #77528 
to clarify that status.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=77452


--
Edit this bug report at https://bugs.php.net/bug.php?id=77452&edit=1

-- 
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to