To be fair, 2.3 is already 8.4 compliant, at least compliant enough for an addon vendor's forum
XenForo 2.3.x is already fully supported on PHP 8.3 and is the currently recommended version.
Wise man. You don't have idea how much.but if developers are happy I'm happy.
If developers are happy, AI agents are happier.Probably things I don't understand lol but if developers are happy I'm happy.
I'd be interested to know if the rapid advancement of AI actually slowed down the development of XF — for the time being — so what they wrote / are writing could be double checked / bug free, and because of that, if we'll see fewer betas and RCs before a version release. 
I'd be interested to know if the rapid advancement of AI actually slowed down the development of XF — for the time being — so what they wrote / are writing could be double checked / bug free, and because of that, if we'll see fewer betas and RCs before a version release.
I'm certainly finding my own recent development progress has slowed significantly while I use AI to help me build out my automated testing systems through extended unit testing; static analysis; container-based automated builds for testing specific configurations and php/platform combinations, etc.
It's fantastic to be able to tell my agent to go and build a XenForo site, install an old version of my addon, then test the upgrade process using the new version, while I continue working on something new. Or tell it to go and test various combinations of XenForo and PHP version - for example: let's see if my addon works as expected on XenForo 2.2.0 with PHP 8.1 and also on XenForo 2.3.13 on PHP 8.5, etc. This is all time-consuming work that often gets dropped because there's only so many hours in a day - but now it's an automatic part of our development process.
Note - I'm not just talking about CI work here - this is an agent actually building and exercising the install and doing various tasks to test that things are working in a much more sophisticated way than a CI runner would typically do, especially given it can diagnose issues and then go and propose a fix for them rather than just reporting success/failure.
I'm expecting that the future benefits of this work will be significant where turnaround times on testing new releases is dramatically faster, and I hope that my code - being much more thoroughly tested now - will also be more robust.
Similar threads
