I understand the docs are still a work in progress; so this is intended to help me (and others) avoid unnecessary pain until the upgrade process docs are more polished.
In Safari Browser: Homepage Images Don’t Appear, @pkarw kindly suggested that I upgrade from my current VSF v1.10.4 to v1.11, but I’m not sure which approach to take. (I assume I have v1.10.4 based on the “version”: “1.10.4” in my VSF root
This cookbook page seems to suggest that we need to painstakingly inspect every file in the entire VSF app directory and perform a manual diff operation on every file. There’s probably a faster way with pure Git commands, but I’m not a Git ninja yet (I use SourceTree.); so this is looking like a pretty daunting process.
I also see there are multiple branches (e.g., v1.11 and v.2.0). And I see @FilipRakowski 's Vue Storefront 2.0 post from many months ago, but there’s no recent activity on that post or in the corresponding GH branch.
When I started working with VSF, one of the most compelling selling points that I understood from various docs is that the upgrade process is supposed to be easy because all the core files are separate from the theme files. I also thought that this easy upgrade process was applicable to the current stable master branch, which appears to be based on the v.1.10.x code that I currently have installed.
Now I think there might be some discrepancy between my perception and reality. More specifically, it seems like that selling point is primarily related to the 2.0 version, not the 1.x version. So, can somebody please clarify the best practice for upgrading? Also…
What is the ETA for the 2.0 version?
Will there be a straight-forward upgrade process from 1.x to 2.0 or is that expected to be a long, tedious process for sites that have heavily modified child themes? (Based on the default theme of course.)
Thank you in advance for providing more clarity on the upgrade process.