Top four reason you must upgrade any Magento 2.0/2.1 to 2.2
Magento 2.2 is out. I have not been able to count the bugfixes on the release notes page but there are a lot.
Nor has Xumulus been able to fully understand the impact of upgrading 2.x to 2.2. But what we do know is there are lots and lots of bugs fixed and may have been out for some time. One of the earliest bugs was filed in GitHub-3545 around Feb of 2016. That makes it about a year and half old. So I am not sure why but Magento was deferring many of its bug fixes to the 2.2 branch. This is very apparent if you read the release notes of 2.1.7, 2.1.8, 2.1.9 or the entire 2.1.x branch. It seems as if 2.2 is much bigger and better.
So, what does this tell us? For one thing, it tells us it’s probably a critical upgrade. Which is confirmed by our contacts at Magento. Based on our 2.1 clients we can attest to the fact there are a large number of open issues with Magento, and you probably don’t want to be on that branch. So here are 3 good reasons to upgrade.
- For every 1 bug you might get new, 10 probably get fixed. Don’t be afraid new bugs are going to introduce! Though this is an issue in many stable software releases, you don’t have the luxury with Magento 2.
- Do you have a project you can’t get live? Is your Magento 2 project stalled in testing? Well, this might just unstick it.
- Rapid upgrade releases are our motto for Magento. If you can keep rapidly pushing forward, the small amount of upgrade issues you have incrementally seems to outway the amount that builds up as you get a wider gap from 2.0 to 2.2 and then to 2.3 etc. Also, we don’t think the 2.1 or 2.0 branch is all that stable, to begin with, so let’s move on up.
- On our bug calls with Magento we heard a lot about how things were fixed in 2.2, then a backported patch was pulled out of the 2.1 branch. So that definitely tells me you want to be on the 2.2 branch if you can, as not every bug can get backported.
Now, I suppose this would bring up a natural question for any Magento 1 users. Should we upgrade to 2.2? Now, unfortunately, there is no real way for us to make a quality assessment on that as users are on all different levels for M2 but it is certainly starting to look like it’s at least starting to stabilize a bit and after 2 years from the initial release it’s about time.