#13311 [Opn->Ana]: status, severity, and category should be distinct in bug database
| From: | goba@php.net | Date: | Tue, 07 Jan 2003 21:04:00 +0000 |
| Subject: | #13311 [Opn->Ana]: status, severity, and category should be distinct in bug database | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-14826@lists.php.net to get a copy of this message | ||
ID: 13311
Updated by: goba@php.net
Reported By: jeroen@php.net
-Status: Open
+Status: Analyzed
Bug Type: Website problem
Operating System: http
PHP Version: 4.0CVS-2001-09-14
Previous Comments:
------------------------------------------------------------------------
[2002-11-13 10:23:23] goba@php.net
Hey these are reminders for Jim, or anyone else who will participate in
developing the new bug system :O
------------------------------------------------------------------------
[2002-11-13 07:42:17] nicos@php.net
Too old.
------------------------------------------------------------------------
[2001-10-20 02:20:44] jimw@php.net
just a new summary.
------------------------------------------------------------------------
[2001-09-14 19:58:49] jeroen@php.net
The categorization of bugs is a bit strange. A more natural and IMO
better solution would be:
- status (open, closed, assigned, ...)
- Type (feature request, cricial bug, performance problem, crash,
security problem, Bogus, Documentation problem, ...)
- Category (arrays-related, IMAP, website problem, ...)
Currently there cannot be a closed critical bug, (would be interesting
for historical purposes, which critical bugs were in 403?), no
categorization of feature requests, etc etc.
I would have liked to classify this bug as website problem:
feature-request, but since category and type are mixed up, I can't...
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=13311&edit=1