As we head closer to the vote - and in light of what I said towards the end of my message in https://externals.io/message/106256#106278, as well as the points Dan articulated regarding the current issue of negative feedback not getting the same level of visibility as the RFC itself - I'd like to figure out a temp solution until we amend our rules.
George - are you OK with having a section that illustrates the issues that me and some others have brought up with this deprecation in the RFC itself? Or add a link to a separate page, along the lines of what Dan proposed? Thanks, Zeev On Tue, Jul 23, 2019 at 8:55 PM G. P. B. <george.bany...@gmail.com> wrote: > Hello internals, > > Due to the controversy after the initial vote on the Deprecate PHP's Short > Open Tag RFC [1] here is a new RFC to deprecate them written with the help > of Nikita Popov <ni...@php.net>. > > This RFC is targeting PHP 7.4 and has an exemption to land after the > feature freeze granted by the Release Managers of PHP 7.4 Derick Rethans < > der...@php.net> and Peter Kokot <p...@php.net>, CCed to this email. > > https://wiki.php.net/rfc/deprecate_php_short_tags_v2 > > Discussion is expected to last 2 weeks followed by a 2 week vote such that > this RFC may land in PHP7.4Beta3 as per the timeline. [2] > > The only point of contention of this RFC that I potentially see is the > removal in PHP 8.1 after short open tags being a Parse Error in PHP 8.0 > instead of it being removed in PHP 9 after it having had a whole major > version release cycle. > > Best regards > > George P. Banyard > > [1] https://wiki.php.net/rfc/deprecate_php_short_tags > [2] https://wiki.php.net/todo/php74 >
