Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95586
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.220.176 cause and error)
MIME-Version: 1.0
Date: Fri, 2 Sep 2016 12:32:27 -0700
Message-ID: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1149a728077efd053b8b645f
Subject: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: me@daveyshafik.com (Davey Shafik)

--001a1149a728077efd053b8b645f
Content-Type: text/plain; charset=UTF-8

Hi internals,

I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove
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 run
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, so
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 introduction
of composer/pickle.

- Davey

--001a1149a728077efd053b8b645f--