Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104917
MIME-Version: 1.0
References: <CAJW__o1hA1DOp4Lf0LA2To5L-8c66+woFgoXAwfLaxxOiEwOPg@mail.gmail.com>
In-Reply-To: <CAJW__o1hA1DOp4Lf0LA2To5L-8c66+woFgoXAwfLaxxOiEwOPg@mail.gmail.com>
Date: Sun, 24 Mar 2019 13:39:36 +0100
Message-ID: <CAAfnsFXtzhEYSPNi-SGT9XeQRhNoS+Fe70ok6CjkOceyhMsEnw@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Cc: Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Unbundle ext/interbase
From: peterkokot@gmail.com (Peter Kokot)

Hello,

On Fri, 22 Mar 2019 at 14:26, Kalle Sommer Nielsen <kalle@php.net> wrote:
>
> G'day internals
>
> I'd like to start the discussion for the future of the ext/interbase extension:
> https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase
>
> The rationale for pushing this extension out of the core is mentioned
> in the RFC.
>
> Unless there is any serious issues raised here, then I will put this
> into voting on Monday 8th of April, noon EET (which is a good two and
> a half weeks away). The intended voting period is set for 2 weeks,
> meaning if voting proceeds, the pools will be closed around Monday
> 22th of April, noon EET.
>
> --
> regards,
>
> Kalle Sommer Nielsen
> kalle@php.net
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

I'm all in for helping out here with both users using this and
maintainers that need to worry about if this extension is even working
ok. However, just one quick thought. The deprecation usually means
that some functionality will cease to exist. And users usually expect
and consider removing deprecated usage from their code and move to
something else. Not that they will have an option to install it over
PECL in PHP 8.0... Is this ok approach for this case? Because with
this approach PHP is also saying quietly that PECL is a museum for
extensions and not a place for developing them further. I might be
completely wrong here though...
-- 
Peter Kokot