Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103862
MIME-Version: 1.0
Date: Mon, 28 Jan 2019 11:21:53 +0100
Message-ID: <CAF+90c98Spnsrg2RhCJi1uv0Z0Ke2q3fhoKyHCnNjnL7V4hNwQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a116be0580820ca3"
Subject: PHP-7.4 branched, master is PHP 8.0
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000a116be0580820ca3
Content-Type: text/plain; charset="UTF-8"

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

--000000000000a116be0580820ca3--