Title: pgodd's Replies | WordPress.org

---

# pgodd

  [  ](https://wordpress.org/support/users/pgodd/)

 *   [Profile](https://wordpress.org/support/users/pgodd/)
 *   [Topics Started](https://wordpress.org/support/users/pgodd/topics/)
 *   [Replies Created](https://wordpress.org/support/users/pgodd/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/pgodd/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/pgodd/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/pgodd/engagements/)
 *   [Favorites](https://wordpress.org/support/users/pgodd/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Backup & Restore Dropbox] You're not doing updates correctly!](https://wordpress.org/support/topic/youre-not-doing-updates-correctly/)
 *  Thread Starter [pgodd](https://wordpress.org/support/users/pgodd/)
 * (@pgodd)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/youre-not-doing-updates-correctly/#post-8023520)
 * You are one angry little dude aren’t you?
    I am not a competitor. Your problems
   with others are not my doing. Perhaps you should consult someone about your paranoia?
   Who cares what you think, with an attitude like yours? You do not command the
   reviews. A review is an opinion of the product, and the user experience. I have
   been honest. You, however are acting like a child. Have fun with that. Back to
   one star.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Backup & Restore Dropbox] You're not doing updates correctly!](https://wordpress.org/support/topic/youre-not-doing-updates-correctly/)
 *  Thread Starter [pgodd](https://wordpress.org/support/users/pgodd/)
 * (@pgodd)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/youre-not-doing-updates-correctly/#post-8023505)
 * Thank-you.
    I don’t wish to be angry with the developer. But security alerts 
   up to 4 times a week for files changed without my permission is an inconvenience.
   With no notice and no versioning, I cannot tell if this is legitimate or a result
   of hacking. This means I have to review the code and look for malicious code 
   each time a change is pushed. LIke I said. The plugin has excellent functionality
   and is very easy to use. The developer can be proud of his skills. But he should
   be conscious of the effect of this practice, and potential clients should be 
   aware of this too.
 * I see he has updated the change log which is excellent. But this morning I was
   greeted by yet another warning that code had changed without my permission. I
   have raised my rating to 3 stars due to the developer’s quick response regarding
   the issue with changelog updates.
 * I understand he is proud of his work and a bad rating is upsetting. If the problem
   with pushing unannounced changes is addressed I would be happy to give this plugin
   a 5 star rating.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Backup & Restore Dropbox] You're not doing updates correctly!](https://wordpress.org/support/topic/youre-not-doing-updates-correctly/)
 *  Thread Starter [pgodd](https://wordpress.org/support/users/pgodd/)
 * (@pgodd)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/youre-not-doing-updates-correctly/#post-8023503)
 * I gave the one star because you are doing the development wrong.
    Today AGAIN
   you pushed a change without notice. I am dropping your plugin and installing 
   one whose developer follows some simple rules.
 * You should thank me for not posting this complaint to the main forum. Your plugin
   could be de-listed. You are doing a prohibited practice. This is not a support
   problem, this is a bad developer problem. You got the rating you deserve.
    I 
   can see you are skilled. But you think the rules don’t apply to you?
 * Plugin Developer guidelines:
 * 14. Frequent commits can be seen as gaming the Recently Updated lists. Try to
   limit commits to prevent this. All commits should include a commit message describing
   the content of the commit, in reasonable detail. **Frequent blank commit messages
   makes it hard for other developers and users to follow what is changing in the
   plugin. Blank commit messages may also be cause for rejection of the commit or
   removal of the plugin from the directory.**
    15. **All code changes to a plugin
   that has a Stable Tag of “trunk” must result in the version number being upgraded.**
   For the trunk and tags method, trunk can be continually updated without version
   number changes, while tags should generally not be updated ever past the initial
   tagging.
 * So who deserves to be sorry?

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