There are two things to consider:
Security
It is essential to use at least PHP versions that have security fix
, that even if they do not receive new updates, they have fixed vulnerabilities.
To know the life cycle of PHP, there is an official link with a reasonably clear chart, in the following link:
http://php.net/supported-versions.php
Using the versions that are still on the chart for the current date, everything is OK. Knowing the end of the product lifecycle helps you organize to upgrade in time to take no risks.
Resources
With each new version, the available features are changed, new features are added, existing features are improved (not always, but it is expected), and there are usually internal improvements of functionality, increasing the speed and stability of the language (within what the PHP base allows).
Some functions are removed, or marked for removal (indicated in the documentation as deprecated, often translated wrong to "depreciated", which is not the same thing).
This alone is no reason to upgrade, if you don’t really need these improvements. Often the risk of breaking some existing application does not justify the rush in changing versions.
For version change, it is recommended to consult the changelog and update notes with care, and evaluate where this will affect your applications.
The most detailed guidelines for change of version are here:
http://php.net/manual/en/appendices.php
By following these guides, you can anticipate and update the applications for a smoother change, and then do the upgrade.
Other components of XAMPP
Activate PHP as the most complex element in the set, but the same reasoning applies to Apache Mysql/Mariadb and any other component.
I would recommend, including, nay use XAMPP in these cases, but install separately each of the components, because the life cycle of each is completely different. XAMPP is excellent for quick installation on a development and testing machine.
For use in a production environment, it’s starting to remind me of those old Tvs that came with a built-in VHS device. It can be convenient when installing, but if you need to change/fix anything, it is more work.
In short, the PHP lifecycle is here: http://php.net/supported-versions.php - The least you can use is versions with security fix, the rest is detail.
– Bacco
Because, it is a system of frequent use, and I am analyzing better so that it does not end up affecting, causing problem, waste of time, to solve. And with that, I will make a backup and test first on the test machine before. Thanks more help from all. : D
– Master_Ranger
Between 5.5.x and 5.6.x there will be no significant changes that cause disorders. Maybe some regex or a return of function give dick, but there you fix without much difficulty. If you want less work, don’t skip straight to 7. But I recommend you try migrating to this latest version php7 so you don’t get stuck in time. The market will run you over if you stop on the way.
– Daniel Omine