README.md steps for reporting bugs should be updated to mention github issues instead of bugs.php.net

[TysonAndre]

Description

The README currently says:

Bug fixes do not require an RFC but require a bug tracker ticket. Open a
ticket at bugs.php.net and reference the bug id using
#NNNNNN.

Fix #55371: get_magic_quotes_gpc() throws deprecation warning

After removing magic quotes, the get_magic_quotes_gpc function caused a
deprecated warning. get_magic_quotes_gpc can be used to detect the
magic_quotes behavior and therefore should not raise a warning at any time.
The patch removes this warning.

https://wiki.php.net/rfc/github_issues#proposal changed this:

Bug reports and feature requests are filed on GitHub with custom issue forms. Security issues point to bugs.php.net instead, because GitHub currently does not support private issue reports.

It may be useful to also update the README in older minor versions of php that still get released?

https://bugs.php.net/report.php mentions the new steps.

---

Should creating an issue be optional if there's a GitHub PR fixing the bug?

PHP Version

N/A

Operating System

N/A

[cmb69]

It may be useful to also update the README in older minor versions of php that still get released?

I think we should update that for PHP-8.0+.

Should creating an issue be optional if there's a GitHub PR fixing the bug?

Generally, I prefer a separate issue, but something like #7723 might be fine without.

[Danack]

Should creating an issue be optional if there's a GitHub PR fixing the bug?

Optional is probably right. Issues and PRs share the same number scheme and users are redirected to the correct url, if they put the wrong (issues|pull) in the URL

e.g. github_com _ php _ php-src _ issues _ 7732 =>github_com _php _ php-src _ pull _7732

also, github fixes up the link in the ticket....which is a little annoying.