Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106692
To: Sara Golemon <pollita@php.net>
Cc: Trevor Rowbotham <trevor.rowbotham@protonmail.com>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <FZ3PBEDob1t-m1TcLhLjyWmEY4VMbZ0LBkx297AVzbtWzuX2y6ZWKRE5Hy4e4Ytx9-VBS6Vr0RpR88jccgfUdktB9c1aNCT0GbxnfvVMAzc=@protonmail.com>
 <13a3e8c2-30c1-d0be-2ba6-6541c91581b9@gmx.de>
 <CAESVnVpXmmGFPpaaHMvrUuoR7O89N=woUb5MYk7UjVb24KeMXg@mail.gmail.com>
Message-ID: <095d5b98-2856-2686-7bfe-d153f03f30db@gmx.de>
Date: Thu, 22 Aug 2019 17:00:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAESVnVpXmmGFPpaaHMvrUuoR7O89N=woUb5MYk7UjVb24KeMXg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: PHP 7.2 minimum ICU version
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 22.08.2019 at 15:54, Sara Golemon wrote:

> On Thu, Aug 22, 2019 at 2:28 AM Christoph M. Becker <cmbecker69@gmx.de>
> wrote:
>
>> On 22.08.2019 at 01:17, Trevor Rowbotham wrote:
>>
>>> Is there any way to increase the minimum required ICU version in PHP 7=
.2
>> and 7.3 to
>>> at least 4.6, which would ensure that the upgrade path is actually
>> available to users
>>> trying to avoid the deprecation notice?
>>
>> We usually do not raise any dependency requirements for stable release
>> branches, to avoid potential BC breaks.  And after all, most of ext/int=
l
>> is supposed to work flawlessly with such ancient ICU versions, and to b=
e
>> able to get rid of this deprecation notice, building with a newer ICU
>> version is already possible (and, in my opinion, recommendable anyway).
>
> Agreed on not raising the library dependency requirement in branch, but
> perhaps we can smooth the transition a little by only raising the
> deprecation notice *if* the environment actually allows using the
> non-deprecated behavior.  This would have the opposite impact on the act=
ive
> branch of raising the dependency while still providing the facility of a
> deprecation notice to builds that aren't based on ancient ICUs.

That.  In my opinion, even those who use ancient ICU should be made
aware of the deprecation, to avoid issues when they finally switch to a
later PHP version with a newer ICU.

> Or perhaps tailor the deprecation warning a little? (Nevermind, I just
> wrote it out and it gets ugly)
>
> Or perhaps just stick with status quo and add a note to the manual. :D

That might be best.

=2D-
Christoph M. Becker