# PHP-7.4 branched, master is PHP 8.0

- Thread: https://externals.io/message/103862
- Original archive: https://news-web.php.net/php.internals/103862
- Started by Nikita Popov on 2019-01-28T10:21:53+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #103862 — Nikita Popov — 2019-01-28T10:21:53+00:00

URL: https://externals.io/message/103862#103862

Hi internals,

As discussed, we are branching PHP-7.4 early, so we can start development
of PHP 8.0 in parallel. I have created the PHP-7.4 branch just now. What
this means for you:

 * PHP-7.4 is now part of the regular merge procedure. If you are applying
a fix to PHP-7.2, merge it to PHP-7.3, then PHP-7.4, then master.

 * You should not update NEWS on PHP-7.4 for bugfixes that are merged from
older versions. If you apply a fix to PHP-7.2, you should update NEWS in
PHP-7.2 and PHP-7.3 only.

 * Backwards-compatible feature changes can still go into PHP-7.4. New RFCs
can (and usually should) still target PHP 7.4.

 * Backwards-incompatible changes, or changes requiring major internal API
changes, can go into master (8.0). New RFCs with non-trivial
backwards-compatibility impact should target PHP 8.0.

Regards,
Nikita