Req #77452 [Csd]: Issue tracker: Undefined status "Wont fix"

Edit report at https://bugs.php.net/bug.php?id=77452&edit=1 ID: 77452 User updated by: chealer at gmail dot com 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: 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? Previous Comments: ------------------------------------------------------------------------ [2019-05-04 11:45:47] petk@php.net Automatic comment on behalf of peterkokot@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 cmb@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. ------------------------------------------------------------------------ [2019-01-16 23:12:11] petk@php.net See the list of statuses also here: https://bugs.php.net/search.php I guess, it's pretty synced actually, yes. So, except that there are 0 critical bugs, and that the "old feedback" doesn't work like this anymore, because the cron job is too fast for it. ------------------------------------------------------------------------ [2019-01-16 22:53:31] cmb@php.net > 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. > I suggest that we bring this one to the mailing list also (which > one, I have no idea yet), […] I think bugtracker related topics should go to the php-webmaster@ mailing list. > 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). ------------------------------------------------------------------------ [2019-01-16 21:20:12] petk@php.net Hello, thanks for reporting all these issues. Bugs app is indeed in need of refreshments like these also. Bug statuses need to be synced and sorted out to have more logical workflows. Having bug statuses that no one knows what they represent anymore is not much helpful. I suggest that we bring this one to the mailing list also (which one, I have no idea yet), so that bugs everyday users recheck all statuses again. There are more statuses here in need of syncing between the edit buttons and the search page: https://bugs.php.net/stats.php?bug_type=Bug ... some statuses are also probably not needed anymore and are left from the past... ------------------------------------------------------------------------ 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