Lines Matching refs:a
3 Anybody who programs in PHP can be a contributing member of the community that
5 websites is a never-ending one. With every release or release candidate comes a
6 wave of work, which takes a lot of organization and co-ordination.
35 If you are fixing a bug, then please submit your PR against the lowest actively
40 you add a link to the PR in the bug on [the bug tracker](https://github.com/php/php-src/issues)
51 Fork the official PHP repository and send a pull request. A notification will be
52 sent to the pull request mailing list. Sending a note to PHP Internals list
65 If this is the first time you've filed a bug, we suggest reading the
66 [guide to reporting a bug](https://bugs.php.net/how-to-report.php).
68 Where possible, please include a self-contained reproduction case!
91 There are a number of technical resources on php-src. Unfortunately, they are
93 provide a good starting point for learning about the fundamentals of the code
115 We love getting new tests! PHP is a huge project and improving test coverage is
116 a huge win for every PHP user.
118 [Our QA site includes a page detailing how to write test cases.](https://qa.php.net/write-test.php)
128 For newly created tests, a `--CREDITS--` section should no longer be included,
143 If you are having trouble contributing to PHP, or just want to talk to a human
149 Although not a formal channel, you can also find a number of core developers on
261 If you are fixing broken functionality in a [PECL](https://pecl.php.net)
262 extension then create a bug or identify an existing bug at
268 If your change is large then create a
275 Update any open bugs and add a link to the source of your change. Send the patch
291 correctly in a thread-safe PHP.
299 Because PHP is a volunteer-driven effort, more complex changes will require
300 patience on your side. If you do not receive feedback in a few days, consider
312 end users, a brief description and your name might be added to the [NEWS](/NEWS)
319 free to post your questions on the mailing list. Please have a look at the more
322 PHP is developed through the efforts of a large number of people. Collaboration
323 is a Good Thing(tm), and Git lets us do this. Thus, following some basic rules
359 | PHP-8.3 | Is used to release the PHP 8.3.x series. This is a current stable version and is open…
360 | PHP-8.2 | Is used to release the PHP 8.2.x series. This is a current stable version and is open…
377 The next few rules are more of a technical nature:
381 should go to the lowest security fixes branch (i.e 7.4). If a change is not
387 release* version with the given change. In other words, news about a bug fix
389 PHP-5.4/NEWS and PHP-5.5/NEWS but not master, which is not a public released
393 modified several unrelated files, commit each group separately and provide a
396 4. Do write your commit message in such a way that it makes sense even without
404 6. If you modified a function that is callable from PHP, prepend PHP to the
429 When you change the NEWS file for a bug fix, then please keep the bugs sorted in
445 | If you did not receive a copy of the PHP license and are unable to |
446 | obtain it through the world-wide-web, please send a note to |
447 | license@php.net so we can mail you a copy immediately. |
