What's New
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic.
Tagged: versions
Hello,
The “Show products as attributes of another product” module I downloaded and installed in March has the version number 1.0.2. Today I re-downloaded the module, its version number is still 1.0.2 but there are notable changes in the source code of the module (eg.: additions like SHOW_PRICE and others).
Also, your update log page doesn’t list this module being updated recently.
My questions are:
I think it is quite confusing that you make changes but do not publish this fact officially anywhere. Your users spend time on writing support questions, you spend time on answering them. It’s a loose-loose situation for both parties.
Please consider abandoning this practice and change version numbers whenever you introduce changes. Any changes. Last time you forgot to change the version number of Panda 2 in the source code from 2.5.1 to 2.5.2. These things can happen, of course. However, you should have used 2.5.3 as the current version number from that point on, even if the change was one or two character only.
Thank you in advance,
Szabesz
Hello Jonny,
Thanks for the information! Please also consider improving the way you communicate changes.
Some ideas to consider:
Thank you in advance for considering,
Szabesz
Hello,
I see. Anyway, another example is “Removing IDs from URLs” module (sturls) where the last changelog is for 1.1.6 form last year. This module is at version 1.1.11 currently.
Any automated method that helps your clients to check for updates – along with some basic info about whose updates are about – would be welcome. Maybe a “Sunnytoo update checker” module could be implemented to check for updates, it could display the changelogs along with some reminders of how to upgrade.
Regards,
Szabesz
You must be logged in to reply to this topic.