On 10.05.2021 at 17:10, Nikita Popov wrote: > * As was already mentioned, there's no support for security issues, so > we'd retain bugs.php.net for that purpose, at least for the time being.
But even if bugsnet would no longer be required to file any new tickets, please keep it in read-only mode. > * It's worth noting that issues are per-repository, which means that > documentation issues will now live in the doc repo(s), and PECL issues in > the PECL repos. php-src will only have issues relating to php-src > specifically. This is great. ACK. > * The minimum minor PHP version affected should probably also be specified > through a label -- I don't personally search issues by version, but other > people (cmb?) might. If search by version is not common, we can have this > information only in the issue description. The operating system can be a > label as well, though we should only add that if the issue is actually > OS-specific -- this is pretty rare. I rarely search by version; I think I did that as RM during the pre-release phase of 7.3. Most often the version info is pretty irrelevant, since the issue affects all supported PHP versions. In my opinion, having the PHP version in the bug description is good enough for now; we still can add labels if that turns out to be useful. > a) I pretty much never look at bug votes -- though GitHub has thumbs-up, > thumbs-down as an equivalent there. I would actually prefer the GH reactions. The voting feature might still be broken, anyway. > TL;DR Yes, I do think switching from bugs.php.net to GitHub issues would be > beneficial for the project. Details on how to do that need to be ironed > out, but I think the direction is the right one. I'm +0.5 on this. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
