If you need to get the wordpress version in your script, there is a global variable: $wp_version (right now it’s something like ‘3.1-RC3-17376′) It contains the wordpress version. If you need to acquire if from a file, you can read it from /wp-includes/version.php: function getWPVersion() { $path=”/path/to/wp-install”; include $path.’/wp-includes/version.php’; return $wp_version; } WordPress Version Variables … Read more
I would only increase the version number if users needed to download the plugin again. The “Tested up to” variable is not used when the plugin is installed, only when people want to install it or want to upgrade. In that case, the information comes from the server anyway, so you don’t need to force … Read more
Just run this grep command from the command line: grep wp_version wp-includes/version.php
The only reason why the 3.3.3 milestone was marked as completed is because leaving the milestone open interfered with our ticket reports for 3.4.1. (I forgot that milestone closures are reflected in the timeline.) Generally speaking, we assign tickets to the next minor milestone if they are reporting an immediate regression. So, a regression in … Read more
You can find the version in wp-includes/version.php, the $wp_version variable. It can also be found in the readme.html file in the root of the WordPress folder.
I found a solution as an automated service over at http://wpseek.com/pluginfilecheck/ It’s does exactly, what was asked for including the generation of list of used functions and giving a suggestion for the Plugin-Header comments.