On 10.06.2017 at 21:29, Rowan Collins wrote: > On 8 June 2017 08:52:41 BST, "François Laupretre" <franc...@php.net> wrote: >> It would be great, IMO, to open a 'Approved for 8.0' section >> on >> the RFC page now, and your RFC could proudly be the 1st one to enter >> it. > > I definitely agree with this, as I've argued before for a more timeline based > approach to major releases to avoid / reduce a repeat of the "quick, while > 7.0 is on the table" RFC rush, and the "well, 7.1 is still kinda the > beginning of 7.x, so we can break things a little" kludges.
I second that. Consider, for instance, the "Deprecate and remove INTL_IDNA_VARIANT_2003" RFC[1]. It has been decided to change the default of idn_to_*() to INTL_IDNA_VARIANT_UTS46 as of PHP 7.4. But what if there will not even be a PHP 7.4? Also it has been decided to remove support for INTL_IDNA_VARIANT_2003 as of PHP 8.0. What if there will be a PHP 7.42 – would we have to wait for decades to remove INTL_IDNA_VARIANT_2003 support? [1] <https://wiki.php.net/rfc/deprecate-and-remove-intl_idna_variant_2003> -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
