You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's great to hear that @cpearcey took over the role of Product Manager for PHP Agents.
I'm raising this issue already because on the 20th of November in 2025, PHP 8.5 will likely be released.
I would like to see that New Relic takes the PHP release cycle serious and gets their act together, to ensure compatibility on the release day. For years, this has been a big pain point for many customers out here.
Improve communication by openly explaining what is being worked on (instead of linking to private tickets).
Start testing the beta's and release candidates
Make sure the changes needed, are already shipped to the main branch when they are ready
Make it possible to install the agent on the new (unsupported) PHP version with an override. This could allow people to start testing on their side and provide feedback back to you.
I think the last point is crucial, as this would give people the opportunity to just go ahead and run it on their own risk. Especially when NR tested the RC's, this should be doable.
Also, these people will be the first to provide crucial feedback if things are working as expected.
The text was updated successfully, but these errors were encountered:
It's great to hear that @cpearcey took over the role of Product Manager for PHP Agents.
I'm raising this issue already because on the 20th of November in 2025, PHP 8.5 will likely be released.
I would like to see that New Relic takes the PHP release cycle serious and gets their act together, to ensure compatibility on the release day. For years, this has been a big pain point for many customers out here.
Some idea's on how to improve this:
I think the last point is crucial, as this would give people the opportunity to just go ahead and run it on their own risk. Especially when NR tested the RC's, this should be doable.
Also, these people will be the first to provide crucial feedback if things are working as expected.
The text was updated successfully, but these errors were encountered: