• Software solutions like this does not need a process of updating it every two days, nobody, even a sysadmin has this much time to update plugin every day.

    Too many releases are not good, it just means they do not test the plugin properly. And, this also means, too many ad hoc changes in code, rather than collect and aggregate them into releases

    Besides that, it is underperforming in many cases, including error with google amp crawler. If you read the other reviews, there are many reporting this issue.

    I would strongly suggest, since you are selling this plugin. The software release cycle should come with full UAT+functional+Regression (Full QA) testing before sending out release it to the public online. This will reduce a lot of 1 stars in the reviews.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    We actually do a full QA and testing before releasing an update.

    Our philosophy is that if we find a bug or a problem, we must not wait for ‘release cycle timeline’ in order to fix it.

    We actually have a release cycles for the features.

    Where are your thoughts on our point of view?

    • This reply was modified 6 years, 3 months ago by Ahmed Kaludi.
    Thread Starter Ruhani Rabin

    (@ruhanirabin)

    Thanks for replying Ahmed,
    I think it is a good way to go: We actually do a full QA and testing before releasing an update.

    My point of view is that almost every day there is an update, so it is impossible to know whether this release is stable or not. I think it is possible to make it weekly updates too. And of course, there are critical vs non-critical updates.

    You can even do it with A/B testing if the user wants. Imagine a day to day person is using this, but have no idea if the functions are stable or might break the site.
    As an ex plugin author, I have nothing against the plugin. In fact, I would love to see the betterment of it. I have gone through the frequent updates process and slowly understood that too frequent updates can create different levels of problems.

    Give it a thought, I am not saying that you change the process immediately. But think about it from many different types of user perspectives.

    I also think so, and also feel amp too much err on the webmaster of any recent updates of such plugins, the lightning marks are red, spending time on optimization. As if they force us to subscribe to their Add-ons.

    On their website there is no chat discussion forum about the plugin, I think they cover it.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Not thinking ahead’ is closed to new replies.