I'm hopeful, but just doesn't seem practical. I've talked to a ton of other XC5 owners and the bugs are endless. It would seem the focus should be more on bugs.
The problem with the new versions, is that there is no way to know if it breaks the logic of a custom mod or other mods. So every upgrade becomes a new site all over. Just when you tackled the bugs, you start all over with a new version. There is no way for the script to pre-predict breaking the logic of a module and in a production environment, merchants loose money.
The upgrades between versions in XC4 were much more seamless and with less headache. I'm not quite sure you guys keep updating the core so often. I would trade stability for features any day of the week right now, because the goal of a merchant is to make sales.
Quote:
|
Originally Posted by xim
One of the main important point in the current requirements for 5.3 - is to save the upgradability for existing merchants. We understand that the changes are huge, but we are going to make the adaptation process very simple.
We already have the beta of the Flexy->Twig script convertor to re-code all the files automatically, we will share it with the community after QA phase. So we will invest a lot of resources to save the upgradability and help our merchants and developers to reduce the adaptation costs.
|