Friendly reminder of development guideline rule #14

Hello @magictrashcan

I’m really sorry, but I do not agree that we are “breaking” any development guidelines here. We release a weekly update, as many, many other developers do. Other urgent fixes as pushed as needed, to mitigate any unforeseen issues.

So, I can tell you for sure that we are not doing anything out of the ordinary or anything that would break any rule. If you were to look at our change log on our website – https://creativethemes.com/blocksy/changelog/ – you will see that 90% of these updates are indeed new features and bug fixes. The other “general fixes and improvements” updates are usually just code maintenance updates as no new features have been added for Free users in that said update.

Hope this clears things up!

Thanks.

That is simply not true:
https://projectdmc.org/plugins/blocksy-companion/#developers

Sometimes you push several times a day and relatively often two days in a row.
Perhaps you should get into the habit of testing more thoroughly before publishing.

@magictrashcan Couple of things:

1. We did push 2 times a day at most (not several times) but this happened extremely rarely. In the changelog you will see that it happened in the period after we released Blocksy 2. At that time, we were still stabilising everything and had to push updates much often than usual. We did because we had to, not because we wanted.
2. Yes, updates pushed two days happened but, again, it happened only because we had to. It only happens when the thursday’s causes problems and in that case we also push one update on friday, to mitigate it. Never in other situations. I assure you we test a lot internally and we also deliver a lot of beta versions to our customers before pushing the actual live release.

I assure you we have an entire pipeline internally that we use for testing our theme & plugin and only code that is tested will make it into the final release that goes live. And we certainly don’t use the SVN repository as a development one, we maintain our own development repository on GitHub, and I can show you the amount of individual commits that goes into one such release.

We try to keep the rhythm of updates steady to make sure everyone is getting the fixes for the problems that they’re having as soon as possible. This is the only reason.

I’m sorry this caused you maintenance hurdles, but honestly, I never heard anyone complaining that a product has too many updates. Isn’t this a sign of a healthy product with a steady development pace?