Magento 2.3.2 involves a lot of changes. While upgrading some clients has been relatively smooth (for a Magento 2 upgrade), those with large numbers of extensions or customizations are especially problematic. In fact, for some clients a rebuild is actually in order – something we haven’t experienced in the past.
Our research revealed that the pace of change in the Magento 2 codebase, rather than stabilizing, is accelerating.
The chart below shows a comparison of the Magento code base when comparing 2.0 to 2.1 versus when comparing 2.1 to 2.3. We’ll probably do an update of the research for 2.1 to 2.2 and 2.2 to 2.3, but, the scope of this analysis was for projects moving from 2.1 to 2.3.
|From 2.0.x to 2.1.x||From 2.1.x to 2.3.x|
This is the number of times the code base was edited and updated. It’s a good surrogate for how much surgery was done on the code.
The number of unique files that were changed between versions.
|Lines of code changed|
The number of lines of code that were changed.