When you have a large solution - multisite CMS with Commerce - upgrading packages do almost always mean, getting new bugs. And if you are fast on updates, you will most probably be the one debugging for hours and doing the job with/for Episerver developer support.
I suggest stable releases! Together with continuous releases.
What if Episerver could pin-point some versions on their main product packages every year that will only get updated with bug fixes, and not features or major underlying hidden changes (cause it does happen).
Example: Last versions before major versioning should always be upgraded with known bugs.
Meaning if version 12.18.2 is the latest version before 13.0, and if bugs exists and is found in 12, it should be fixed to that stable version. e.g. 12.18.3 and the latest 13.0.1 and so forth until Episerver pin-points a new stable version, e.g. 13.6. And then probably the last version of 13.
This means Episerver needs to maintain two version in their code base and continues release life cycle. Some will say that is not possible, but the advantage must be greater and worth it in my honest opinion.
Advantages
- Customer would be confident going to a stable release
- Cost effective for customers
- Customer confident with Episerver being best choice
- Partners can focus on building awesome solutions and not debugging errors for Episerver
Please upvote on left side if you feel you recognize the problem and/or write your story around this below.
Blog post: https://devblog.gosso.se/?p=1096
Thx