Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111328
MIME-Version: 1.0
References: <CAP=4hCLm0qOBkCiynKcYJQXHGMvykv19otQYfig9t_rQf771VA@mail.gmail.com>
 <CAF+90c8d+q4y31tHSTehw8GQ6gBCeVu-JFEG4T+SJ2eN_967xQ@mail.gmail.com>
In-Reply-To: <CAF+90c8d+q4y31tHSTehw8GQ6gBCeVu-JFEG4T+SJ2eN_967xQ@mail.gmail.com>
Date: Tue, 4 Aug 2020 13:22:24 -0500
Message-ID: <CAESVnVpzFQqgmSkriLw1hycgP+7sm69fRX1aD5eVGkJjR5_Ung@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="000000000000daf47105ac1156e0"
Subject: Re: [PHP-DEV] 8.0 Feature Freeze happening today
From: pollita@php.net (Sara Golemon)

--000000000000daf47105ac1156e0
Content-Type: text/plain; charset="UTF-8"

On Tue, Aug 4, 2020 at 12:01 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Sorry, I didn't catch that this message said feature freeze *and branch*.
>
> Please do not create a separate PHP-8.0 branch yet. A separate branch is
> only needed if anyone wants to start landing changes targeting PHP 8.1
> already -- as far as I'm aware, nobody is actively working on PHP 8.1 yet.
>
>
This is how we've done it since we adopted the formalized release process.
:/


> Due to our git workflow, creating a branch now means that every single
> commit to PHP 8.0 will also require a merge into master. This is a rather
> big waste of time and CI resources if we expect PHP-8.0 and master to be
> identical in the near future.
>
>
I, for one, plan to start pushing resource->object conversions that are
targeting 8.1, so to me it makes sense to have that development branch open
already.

Do others feel strongly one way or the other?

-Sara

--000000000000daf47105ac1156e0--