On 10/05/2021 16:10, Nikita Popov wrote:
Did I miss anything else that bugs.php.net <http://bugs.php.net> does?
The biggest difference I see between GH Issues and every other issue
tracker I've ever seen is pre-defined fields. Labels can broadly do the
same job, but they feel very different when managing them, composing
search queries, and viewing search results.
The fields on the Advanced Search for bugs.php.net are currently:
* Status - GH has only "Open" and "Closed"; we'd probably want a set of
"Status-..." labels
* Type - "Feature Request" is probably fine as a label; "Documentation
Problem" would probably be the doc-en issue tracker, but I don't know
how easily issues can be moved from one project to another during triage
* Project - PHP or PECL; again, possible requirement to move issues
between projects?
* Package - as you say, this is a long and unwieldy list right now, but
one that needs to exist in some form (i.e. re-organizing it to a smaller
list is somewhat orthogonal to moving to a different platform)
* OS - makes sense as optional labels for "Windows-specific" etc
* PHP Version - as you mention, what to do with this depends how people
use it (and also how reliable it is)
* CVE-ID - irrelevant if security issues are going somewhere else
* Assigned - exists in Github!
* Author email - exists in Github!
* Has patch - redundant
* Has pull request - not sure if you can search on this in Github, or if
we'd have to add a manual label (again, this is the kind of thing a lot
of projects maintain bots for)
* Commented by - exists in Github!
Regards,
--
Rowan Tommins
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
