I want to upgrade spring framework from 4 to 5. Should i go with latest version such as 5.2.6 or any prior version i.e 5.2.0 or 5.2.4 etc? How should i decide on this ? I don't have any specific feature in mind.Thanks,
Don't see any reason not going for the latest.
Usually the major releases (from 4 to 5) might break something, so you might want to wait if it requires a lot of changes on your side, but if you're going to move to 5.2.x - go for the latest
Related
In one of our website we are using CKEditor version 4.5.4. After Penetration testing, upgrading the CKEditor version to the latest one is recommended.
Functionality point of view we don't want to change anything. So, to which version we should upgrade either to 4.20.0 or to version 5. The target is to remove vulnerabilities.
I want to upgrade my ES cluster(current version: 7.6.2) to the latest version (7.15.2 until now)
Is it ok to upgrade directly to the latest version or should I upgrade with 2 or 3 steps on different version?
For instance, for upgrading mongo db, it should be upgraded step by step to the next version...
I just want to know what is the policy or even best practice for upgrading ES ?!?
Thanks
It's totally fine to update between minor versions (7.x -> 7.y) as well as one major version up from latest minor version (6.8 -> 7.y), see upgrading document for the details. Best of all, it can be a rolling upgrade so you can upgrade nodes in the cluster one by one without cluster downtime or data loss. Just make sure cluster health is green before moving on to the next node.
From which version I should start learning Spring framework?
I am confused from which version I should start, there are multiple major versions strating from 2 till 5.
Start with latest version is a general rule of thumb. Unless you are working in an environment (say collaborative project) where you have no choice but to use a specific version.
Docs will have sections explaining concepts for a newbie.
In a framework like Spring major versions have different concepts about how things should be handled and things wouldn't be compatible between versions. Why learn something which is known to be outdated and not supported by newer version.
Newer version also introduce newer technologies and paradigms e.g. Spring 4 introduced websockets and Sprint 5 has support for reactive style and HTTP2.
Also newer version would be fixing what is broken in a previous version.
I have a large project running on Laravel 4.2 and now I would like to upgrade it to the latest release (5.4)
On the upgrading guide I can see the steps to upgrade from each release to the next one, but the 4.2 to 5.0 requires a fresh install. Hence the question: should I install 5.4 (and fix problems) or 5.0 (running each upgrade)?
I'm possibily using any Laravel functionality, and have organized repositories for my own custom methods; I also need to maintain the database. I need to upgrade because I would like to use event bradcasting with Laravel Echo.
Thanks
To those looking for an answer: update directly to latest version, then fix changes along the way.
Explanation:
At first I tried to upgrade version by version; it was a pain. Every single vendor had different packages for each version and that caused issues even before correcting the code. I couldn't start fixing my code because the installation requirements of the vendors were failing at a certain point of the upgrade process.
Upgrading directly to latest version requires the correction of many things, but at least those are only related to your code. In my case I had to remove Sentry (authentication), Laravel OAuth, and some others I don't remember in favor of some native packages which I hope will be maintained properly. The upside of this approach is that once you have all the packages you need installed you can work directly on your code... which is what you have to do anyway.
I'm updating a Joomla page for a friend of mine - and the version currently online (when it's not being brought down by hackers) is 1.5.20. As far as I can see, there are no update patches available to bring this up to date. I'm aware that I can't update this to a 2.x or a 3.x version, but if I at least could bring this up to the newest version of the 1.5.x releases, that'd be good for security.
So, what patch should I choose, and where can I find it?
From the Joomla docs;
If you are on the version prior to the current one, use the file that updates from the prior version to the current version (for example, Joomla_1.5.25_to_1.5.26-Stable-Patch_Package).
If you are on an older version, use the 1.5.0 to current version file (for example, Joomla_1.5.0_to_1.5.26-Stable-Patch_Package).
In your case, since you currently have 1.5.20 and 1.5.26 is the latest 1.5.x version released, the latter would be the correct choice.
Further update instructions are at the above linked docs, read them first, esp. when it comes to backing up the existing site.
There is no patch to upgrade from any Joomla 1.5 version to the current release.
The current Long Term Release (LTR) is Joomla 2.5, the lastest Short Term Release (STR) is Joomla 3.0.
Both of these are not directly upgradeable from any 1.5 version.
Your best bet would be to migrate using a tool such as:
http://extensions.joomla.org/extensions/migration-a-conversion/joomla-migration/15609
Please note that Joomla 1.5 is now unsupported, with no security patches issued to fix any vulnerabilities. Your Joomla 1.5 install will be getting unsecure, very quickly.
As Joachim said, backup first, restore at your leisure.