Hello internals,
As announced last week I've opened the vote for the 8.6 mass deprecation RFC:
https://wiki.php.net/rfc/deprecations_php_8_6
The vote runs for two weeks and will close automatically on the 10th of August 2026 at 13:00:00 UTC.
Please remember that the wiki is only capable to handle a single vote at a time,
so each vote MUST be submitted individually.
Best regards,
Gina P. Banyard
Hi
As announced last week I've opened the vote for the 8.6 mass
deprecation RFC:
https://wiki.php.net/rfc/deprecations_php_8_6The vote runs for two weeks and will close automatically on the 10th of
August 2026 at 13:00:00 UTC.Please remember that the wiki is only capable to handle a single vote
at a time,
so each vote MUST be submitted individually.
It seems the RFC title didn’t make it into the email subject. I'm
sending this reply to fix the Subject for proper visibility. It's still
before 13 UTC, so there's still two full week for the vote.
Best regards
Tim Düsterhus
Hi
As announced last week I've opened the vote for the 8.6 mass
deprecation RFC:
https://wiki.php.net/rfc/deprecations_php_8_6The vote runs for two weeks and will close automatically on the 10th of
August 2026 at 13:00:00 UTC.Please remember that the wiki is only capable to handle a single vote
at a time,
so each vote MUST be submitted individually.It seems the RFC title didn’t make it into the email subject. I'm
sending this reply to fix the Subject for proper visibility. It's still
before 13 UTC, so there's still two full week for the vote.Best regards
Tim Düsterhus
I have missed the "Deprecate define() with $case_insensitive being
specified" before it went to vote, but I wonder why do we need to
deprecate it. If the feature is gone and the deprecation happened
already in the past, then what's left is just to clean it up by
removing the redundant parameter. By removing the parameter we cannot
break any userland code, so modifying the warning message won't help
with anything.