Hi Nicolas,
I loved reading through the changelog, I love the idea of updating to that new version.
I hate the idea of actually doing it, as mentioned before. For no less than 2 reasons:
(1)
Did the count: I have over 40 views edited and modified, some lightly, several heavily. Like probably many other users. And I am still in development, so this is not the end of it, certainly more to come. Without further information of you, I will have to go through each and every file - almost literally each line of it, and compare "my" 2.3.0 with "your" 2.3.1. Probably sometimes only to figure you haven't changed the view at your end. How long will it take me? One whole day? Two? More? Times how many HikaShop users? Looks like tens of thousands of hours burnt which could be used better elsewhere.
(2)
Is the 'current' 2.3.1 the 'final' 2.3.1? During the next days and weeks, will you add mods? When, how many, and which - affecting features as well? So, I'll either miss those as I won't even know, or I'll have to go through the whole check as mentioned here above under (1) - again?
See, I quickly became a fan of HikaShop & Market, not least due to you guys' fast and continuous development and improvement, and your amazing support. But - however you do it - you MUST improve your updating system. We out here are using your product professionally, we're bound to make a living out of it.
I might be the one stating it here, but I swear there are tons more out there who are thinking the same thing, and see themselves stuck with some old version because it's practically infeasable to try and benefit from your improvements - which I thought you're putting all your effort and work in for.
"However you do it"... - suggestion #1:
I'd be already happy if I had a list of views which, since 2.3.0, are changed in 2.3.1 - little or much, I don't care.
Or vice versa, give me the list of files which are NOT affected/changed.
Whichever is easier for you.
Anyway, you can do so, based on file modification dates or however. We can not.
Also - suggestion #2:
As you - brilliantly! - keep coming up with further improvements (as in feature related stuff - the stuff we see front or backend), change the version number so we know, make it 2.3.1.0.0.1 or whatever, add a changelog, and tell us which views are affected.
If you have a better suggestion for yourselves... wonderful. But please, please, please, let us have and use updates without them taking days out of our lives each time, and without knowing if what we downloaded is indeed what version number and changelog say it is, or if there's more to it.
Please, let's stay ahead of the competition. You, and us. Thanks.
P.S. - provisionally:
This has nothing to do with 'auto-update'. Presently, and unless you inform us better on what exactly is affected in the view/file structure, auto-update makes things worse if I don't know at all what's going to happen once I click. Either my site might break, or I might simply not at all notice and benefit as improvements will likely remain hidden under my customised views. So, the way things are now, auto-update is counter-productive, actually even dangerous, for me as user, and I am forced to download the complete package and go through the awkward procedure as described above and before.