I see on my Dashboard that WordPress 3.4 is out today. I knew it would be out soon as I follow the WordPress Hackers and WordPress Testers mailing lists but have not done anything with it yet. In the past I have tried to do a basic smoke test against one of the release candidates before the final release is out but this time I haven’t had the time to do it.
So the answer to “will it work?” is “I don’t know!”. I realize that isn’t a very good answer and I will try to test it in the next few days. My recommendation is to hold off until I’ve done some basic testing. I am not aware of anything that will break based on what I know is coming but until I test it, you never know!
WordPress has a nice built in feature to update plugins when there is a new version available. Because wp-SwimTeam isn’t hosted in the official WordPress plugin repository, I haven’t been able to take advantage of this feature.
I have set up projects in the official WordPress plugin repository for both wp-SwimTeam and phpHtmlLib. I am working on a process where the plugin updater will work by adding the code into the WordPress repository when Iam ready to release it.
Currently the version of the code in the WordPress repository is the same as what is available for download although the version number reported is wrong (1.0.553 vs 1.2.553). The “553” is the critical part of the release number because it represents the Subversion commit number (build number) that the release is based on.
If you see a “plugin out of date” message within the WordPress Dashboard, it is because I am working on this process. The latest and greatest release will likely be available first as a download on this site but when I reach what I consider a “stable” release, I will also make it available through the WordPress plugin repository. Stay tuned as this flushes out.