forgot to tick the box to receive notifications
John-Pierre,
Sometimes we upload very minor fixes that are pertinent to only a small percentage of users, so we don’t increment the version number every single time for every modification since that has been equally annoying for users in the past (i.e. high frequency of having to update plugins). This possibility of annoyance has been particularly true for people who test the plugins on their local or development environments before eventually pushing it to their live site; you can imagine how much work this could take each time.
That being said, your Wordfence use case brings an interesting and valid point, given its comparison algorithm. We’ll think about a middle-ground solution for both updates in general and Wordfence users.
Thanks!
-EmbedPlus Team
Hi,
Thank you for your reply.
I understand the reasoning, this also happens with other plugins who only change the version number to indicate compatibility with the latest version of WP.
Except in this case, there was an actual code change and I believe that should be an actual version change, like maybe a minor version such as 11.5.1.
Some plugins I use have an update every week (like WordFence). And you are right, it is annoying to get these updates all the time. On the other hand, an update only takes a minute.
Anyway, good to know you’ll think about a solution!
Thanks
JP
IMO, this it totally the wrong behaviour and JP has seen the results of that. As a fellow plugin developer ALL code changes should require a version change, however small. It’s up to individual users, via the details in the changelog, to decide whether they need to upgrade so, yeah, keep regular minor changes coming. And, yes, that does include compatibility changes. If no code changes are required after a new WP release then you simply update the README to reflect this. If code changes were made you update.
I’d make better use of more detailed version numbers – using multiple decimal places such as you did with 11.0.1. The first number represents a major release, the second a more minor and the last a trivial one (or emergency bug fix).
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Sometimes we upload very minor fixes that are pertinent to only a small percentage of users
Yeah. Please don’t do that. Really, don’t.
*Looks for coffee*
I get that you don’t want to bombard users with minor updates so if what you’ve really said is true about small percentages of users then queue up the changes and then push it out when you feel it hits critical mass.
I understand the reasoning, this also happens with other plugins who only change the version number to indicate compatibility with the latest version of WP.
Yes, but that doesn’t change the functionality of any code. When you flag plugin as compatible you don’t (and shouldn’t) change the plugin version if you’ve not changed the code.
If the author is changing the code then the version number should increment. Even if the version goes from 11.5 to 11.5.1. That is the whole point of version numbers.
Thanks for the awesome feedback. Your advice has been noted.
Cheers,
-EmbedPlus Team
Just a word from a “common user”: I totally agree – no changes without a notification in form of a update number please.
To me it’s utterly important to have this plugin working 24/7, so I need some way of information to check if it still works with any kind of changes, no matter how small it is.
Just my few words about it 🙂
Cheers
