Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103438
To: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAF+90c8itae3inWZ8W-1GSGFH7W03bzHuOOimkUjbEPMqTEVww@mail.gmail.com>
Message-ID: <091debad-319d-7010-4852-fb9d7e6304ac@gmx.de>
Date: Thu, 15 Nov 2018 16:07:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c8itae3inWZ8W-1GSGFH7W03bzHuOOimkUjbEPMqTEVww@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: Branch off PHP-7.4 early
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 15.11.2018 at 15:27, Nikita Popov wrote:

> Based on previous discussions, it appears that our current plan is to
> release PHP 8.0 after PHP 7.4. Normally we only branch off versions once
> they reach beta stage, which means the PHP-7.4 branch will only be created
> around summer 2019.
> 
> I would like to propose to branch off PHP-7.4 earlier this time and start
> working on PHP 8.0 in the master branch. This will allow people to start
> working on changes that are not suitable for PHP 7.4 (due to either
> significant internal ABI breakage, or userland breakage).
> 
> Because each new branch introduces a lot of merge overhead for
> contributors, I would further propose that merges should only go up to
> PHP-7.4, while merges into master (PHP 8) will be performed occasionally,
> on an as-needed basis, by the people working on it.

Have you considered having a separate PHP-8 branch, which can be rebased
onto master from time to time, and eventually be merged into master
(basically, treating the PHP-8 branch as a big feature branch)?

-- 
Christoph M. Becker