Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103439
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=turbo-smtp; d=php.net;
	h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type;
	b=XUOdDZFs6ksiuglGhupCsHwA4sfDs42EierrDXruxOOnN0FSCNdzpZshOK60yM
	l+P3u74yoqTg8f7VowbTYK6x3E5CkgotBdFPo+5ri2bpyzVNOET4s6d2e6yL6IuK
	ZwK2mU2TVkWf/v6Or4v02sd6R1NTjvwCcfOEUj+z82f74=;
MIME-Version: 1.0
References: <CAF+90c8itae3inWZ8W-1GSGFH7W03bzHuOOimkUjbEPMqTEVww@mail.gmail.com> <091debad-319d-7010-4852-fb9d7e6304ac@gmx.de>
In-Reply-To: <091debad-319d-7010-4852-fb9d7e6304ac@gmx.de>
Date: Thu, 15 Nov 2018 18:46:11 +0200
Message-ID: <CAJHtznxd7XoLH02a4Y4f5vfEbJX7GoJiwXtdGWpVSOkcXNTS9g@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000070038c057ab6ca0d"
Subject: Re: [PHP-DEV] Re: Branch off PHP-7.4 early
From: zeev@php.net (Zeev Suraski)

--00000000000070038c057ab6ca0d
Content-Type: text/plain; charset="UTF-8"

On Thu, Nov 15, 2018 at 5:07 PM Christoph M. Becker <cmbecker69@gmx.de>
wrote:

> 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)?
>

First, I think that continuously merging the level of changes we have in
store for PHP 8 on an ongoing basis from a branch into master - while
master is a moving target - would be a pretty big headache.   That's why I
think there's sense to PHP 8 being the master branch, where most
development would go towards.

However, I think that if PHP 8 is on master - it should become the
responsibility of people who introduce patches for 7.4 - to also ensure
that they work with 8 (master).  If PHP 8 will be in a branch, that's much
less likely to happen.  Given the complexity and effort of 8, I think we
could use some shared responsibility here, instead of putting the burden on
the few working on the PHP 8 magic.

Another option, by the way, would be ditching 7.4 altogether and focusing
our efforts on 8.0 right away.  It does mean people won't get typed
properties in 2019, but it will mean they'll likely get PHP 8 sooner.

Zeev

--00000000000070038c057ab6ca0d--