Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112023
MIME-Version: 1.0
References: <CAP=4hCLJn=O9g=i3gtPNZY_Q4krS=tkbQZasNnvs773mfEV-Qg@mail.gmail.com>
In-Reply-To: <CAP=4hCLJn=O9g=i3gtPNZY_Q4krS=tkbQZasNnvs773mfEV-Qg@mail.gmail.com>
Date: Thu, 8 Oct 2020 09:49:07 +0200
Message-ID: <CAF+90c-A4v=nWt+4wb3rOoUJi-Xj2WE=dGCSUG0bswSOjVVK0A@mail.gmail.com>
To: Gabriel Caruso <carusogabriel@php.net>
Cc: PHP Internals <internals@lists.php.net>, Sara Golemon <pollita@php.net>
Content-Type: multipart/alternative; boundary="00000000000015f35905b124128c"
Subject: Re: [PHP-DEV] PHP 8.0 branch cut - The Return
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000015f35905b124128c
Content-Type: text/plain; charset="UTF-8"

On Mon, Sep 28, 2020 at 10:56 AM Gabriel Caruso <carusogabriel@php.net>
wrote:

> Following Sara's email a couple of weeks ago, I come this week with a
> similar one:
>
> Next Tuesday, Sep 29th, has been marked on our calendars as the branch date
> for PHP-8.0 which would open master up for 8.1 targeted work.
>
> This would mean that bug fixes would need to include PHP-8.0 in their merge
> chain (meaning more work to merge 8.0 targeted fixes).
>
> Please let Sara and I know how you feel about this date. We can see that
> master is still quite active, especially with
> https://github.com/php/php-tasks/issues/18 and
> https://github.com/php/php-tasks/issues/16, and we don't wish to make the
> work to stabilize
> the 8.0 release any more difficult than it has to be.
>
> Thanks,
>

At this point we have a number of PHP-8.1 only changes pending, so I think
it would make sense to go ahead with the branch cut now. Any concerns with
doing that today/tomorrow? (I don't think we need to synchronize this with
the next release.)

Nikita

--00000000000015f35905b124128c--