Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95587
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.220.169 cause and error)
MIME-Version: 1.0
Sender: me@daveyshafik.com
In-Reply-To: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
Date: Fri, 2 Sep 2016 12:36:04 -0700
Message-ID: <CANaX5nctz9NMFsziiKpsFtUieq1OnAKywQnC2EE9E14fxK-azw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1149a728f4a246053b8b70b7
Subject: Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: davey@php.net (Davey Shafik)

--001a1149a728f4a246053b8b70b7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Also, just wanted to say:

As a former fairly major contributor to PEAR (see:
http://pear.php.net/user/davey) I understand that PEAR has a special place
in the heart of many old-school PHP developers =E2=80=94 but I believe that=
 the
community has spoken, through lack of action on PEARs part, and the rapid
adoption of composer on the general communities part.

We should probably also have some conversations about actually sunsetting
the PEAR and PECL sites and deprovisioning those resources. But that's a
whole other conversation ;)

- Davey

On Fri, Sep 2, 2016 at 12:32 PM, Davey Shafik <me@daveyshafik.com> wrote:

> Hi internals,
>
> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remov=
e
> in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+=
)
> in their place.
>
> https://wiki.php.net/rfc/deprecate-pear-include-composer
>
> I highly recommend reading the twitter poll and accompanying thread at
> https://twitter.com/dshafik/status/756337267547832320
>
> I believe that pickle solves the issues with regards to pecl, and have ru=
n
> the idea passed Jordi and Pierre. Both are fine with this RFC. :)
>
> I understand that adding in composer/pickle is just setting us up for
> having a future "Deprecate composer/pickle & Replace with foo/bar" RFC, s=
o
> I've proposed the voting reflect that some people will just want to
> deprecate/remove pear/pecl and not replace them at all.
>
> I'm also proposing voting choices around the optional/default introductio=
n
> of composer/pickle.
>
> - Davey
>

--001a1149a728f4a246053b8b70b7--