Hello internals,
The following RFC https://wiki.php.net/rfc/snmp_improvements_2026 stipulated that the proposed PHP versions for this RFC are: "Next stable release for all currently supported PHP versions."
This goes against our policy regarding versioning (https://github.com/php/policies/blob/main/release-process.rst#patch-version-number).
As such these changes will only land in PHP 8.6.
Moreover, I suggested replacing the new integer constants for the "Implement more MIB parsing and value output controls" part of the RFC by PHP enums to improve type safety from the userland perspective.
I think this is an improvement on multiple levels as it also effectively "translates" the C enums defined by SNMP to PHP enums exposed to userland.
The plan is to have this merged in time for PHP 8.6.0beta2 so people can test this.
Best regards,
Gina P. Banyard
Hi
The following RFC https://wiki.php.net/rfc/snmp_improvements_2026
stipulated that the proposed PHP versions for this RFC are: "Next
stable release for all currently supported PHP versions."This goes against our policy regarding versioning
(https://github.com/php/policies/blob/main/release-process.rst#patch-version-number).As such these changes will only land in PHP 8.6.
Moreover, I suggested replacing the new integer constants for the
"Implement more MIB parsing and value output controls" part of the RFC
by PHP enums to improve type safety from the userland perspective.
I think this is an improvement on multiple levels as it also
effectively "translates" the C enums defined by SNMP to PHP enums
exposed to userland.The plan is to have this merged in time for PHP 8.6.0beta2 so people
can test this.
Thank you. Both amendments make sense do me.
Can you (or Steven) shortly mention the changes in an Errata section in
the RFC so that it's clear to everyone reading the RFC that the final
version differs from what was being voted on? See
https://wiki.php.net/rfc/partial_function_application_v2#errata or
https://wiki.php.net/rfc/redact_parameters_in_back_traces#errata as an
example.
The “Status: Accepted” at the top RFC could be updated to “Implemented”
at the same time.
Best regards
Tim Düsterhus
Hi
The following RFC https://wiki.php.net/rfc/snmp_improvements_2026
stipulated that the proposed PHP versions for this RFC are: "Next
stable release for all currently supported PHP versions."This goes against our policy regarding versioning
(https://github.com/php/policies/blob/main/release-process.rst#patch-version-number).As such these changes will only land in PHP 8.6.
Moreover, I suggested replacing the new integer constants for the
"Implement more MIB parsing and value output controls" part of the
RFC by PHP enums to improve type safety from the userland perspective.
I think this is an improvement on multiple levels as it also
effectively "translates" the C enums defined by SNMP to PHP enums
exposed to userland.The plan is to have this merged in time for PHP 8.6.0beta2 so people
can test this.Thank you. Both amendments make sense do me.
Can you (or Steven) shortly mention the changes in an Errata section
in the RFC so that it's clear to everyone reading the RFC that the
final version differs from what was being voted on? See
https://wiki.php.net/rfc/partial_function_application_v2#errata or
https://wiki.php.net/rfc/redact_parameters_in_back_traces#errata as an
example.The “Status: Accepted” at the top RFC could be updated to
“Implemented” at the same time.Best regards
Tim Düsterhus
Hi,
I've updated the wiki with both the new status and the errata section.
regards
Steve