Adam Ainsworth

Sometimes newer isn’t always better.
You won’t always want to update a given plugin. Perhaps the design has been changed, or a bug has been introduced. Maybe it has been taken over by someone new and they’ve added loads of obnoxious ads or other sneaky monetisation methods. Or perhaps you just like it the way it is.
However, WP keeps telling you there’s a new version available, and lists it along with other plugins which you may actually want to update.
What happens if you accidentally update? At best, it’s a tedious downgrade process, at worst it may completely mess up the data that the plugin was using. In any case, it’s a pain and there’s no ignore update function in WP.
Until now!
IMPORTANT – You should only leave a plugin updated if you know what you are doing, familiar with the risks and willing to accept the consequences should an unpatched vulnerability be exploited on your site.
The plugin author cannot be held responsible for any loss or damages that occur as a result of using this plugin to disregard software updates!

Newer Not Better

Prevents selected plugins bugging you about updates

Adam Harley (Kawauso)

Checks for the presence of the <code>.svn</code> directory in each plugin’s directory. Disabled for plugins with their files directly in the <code>/plugins/</code> directory to prevent false positives.
Also supports other systems through the use of the <code>REVISION_CONTROL</code> constant. Just set this to the directory created by your revision control system in your <code>wp-config.php</code>
Based on <a href="http://developersmind.com/2010/06/12/preventing-wordpress-from-checking-for-updates-for-a-plugin/" rel="nofollow ugc">code</a> by PeteMall.

No Updates for Plugins under Revision Control

Prevents plugins from being updated by the WordPress updater if they are under Subversion revision control (or other systems).

Newer Not Better vs No Updates for Plugins under Revision Control