Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112024
MIME-Version: 1.0
References: <CAP=4hCLJn=O9g=i3gtPNZY_Q4krS=tkbQZasNnvs773mfEV-Qg@mail.gmail.com>
 <CAF+90c-A4v=nWt+4wb3rOoUJi-Xj2WE=dGCSUG0bswSOjVVK0A@mail.gmail.com>
In-Reply-To: <CAF+90c-A4v=nWt+4wb3rOoUJi-Xj2WE=dGCSUG0bswSOjVVK0A@mail.gmail.com>
Date: Thu, 8 Oct 2020 08:56:52 -0500
Message-ID: <CAESVnVq8ZcBNwD5kqcHHo2gW2Of3O=XZ05Zb521jDeyduLf_kA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Gabriel Caruso <carusogabriel@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e67f5805b1293439"
Subject: Re: [PHP-DEV] PHP 8.0 branch cut - The Return
From: pollita@php.net (Sara Golemon)

--000000000000e67f5805b1293439
Content-Type: text/plain; charset="UTF-8"

On Thu, Oct 8, 2020 at 2:49 AM Nikita Popov <nikita.ppv@gmail.com> wrote:

> 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.)
>
>
Traditionally we've done that with a release (on an every other tuesday),
but there's no reason that /has to/ be the case.  No objections from me if
you want to just cut it.

-Sara

--000000000000e67f5805b1293439--