Coreupdater uses now the same type of configuration as Prestashop used before version 1.5: a module combined with a entry in the menu. Prestashop in the end decided that it was more logical to just use the configure page of the module: update modules are regularly updated so you have to visit the module anyway. And Prestashop was clever with the name "1-click updater": it means that the name is alphabetically on the top of the module list so people are aware that it exists.
Coreupdater overwrites my pdf templates (and very likely also mail templates). Prestashop updater didn't do this and I believe that that is the best approach.
I believe that from the marketing point of view "bleeding edge" is not a good idea. You want to radiate stability: that is what people want who base their company on your product. Many prefer an older product as long as they know it is stable. That is why Prestashop 1.6 still is popular. Bleeding edge sounds like programmers trying new things instead of corporate stability.
Another problem is that Bleeding Edge overwrites everything. So it is not really an option for people who adapted their files instead of using overrides - as some people do. My preferred solution would be to overwrite everything only with upgrades to the next (or previous) version. Besides that you would then have a bugfixer that just replaces those files that need fixing for that version (and provides a list).
I hope you find something useful in those considerations.
Coreupdater uses now the same type of configuration as Prestashop used before version 1.5: a module combined with a entry in the menu. Prestashop in the end decided that it was more logical to just use the configure page of the module: update modules are regularly updated so you have to visit the module anyway. And Prestashop was clever with the name "1-click updater": it means that the name is alphabetically on the top of the module list so people are aware that it exists.
Coreupdater overwrites my pdf templates (and very likely also mail templates). Prestashop updater didn't do this and I believe that that is the best approach.
I believe that from the marketing point of view "bleeding edge" is not a good idea. You want to radiate stability: that is what people want who base their company on your product. Many prefer an older product as long as they know it is stable. That is why Prestashop 1.6 still is popular. Bleeding edge sounds like programmers trying new things instead of corporate stability.
Another problem is that Bleeding Edge overwrites everything. So it is not really an option for people who adapted their files instead of using overrides - as some people do. My preferred solution would be to overwrite everything only with upgrades to the next (or previous) version. Besides that you would then have a bugfixer that just replaces those files that need fixing for that version (and provides a list).
I hope you find something useful in those considerations.