Should WordPress plugins that make any database schema changes have a local database scheme version number?
The plugin README file has tags for Requires at least, Tested up to and Stable tag.
I’m suggesting that alongside defining the plugin version, and the three README tags, there should be a value for the schema. This means that plugin authors can explicitly note when their plugin is updating the schema.
Whether it goes in the main plugin file next to plugin version, or in the README file I’m not sure it makes any difference. But if we build in some hooks to trigger on schema version change then we gain two things. Firstly, developers like it as they can explicitly perform tasks based on schema versions and version changes. And secondly, users can be notified that the plugin is about to make schema changes. Which might encourage backups.
I think that’s a win-win!
The first WordPress 3.5 beta has been released.
Read all about it in WordPress news: http://wordpress.org/news/2012/09/wordpress-3-5-beta-1/
Here is my short review: I like it. Buttons are going square again. I don’t want to edit the CSS like that.
Following a series of beta releases, final testing begins with RC1
This is the time when developers, hosts and enthusiast who want a sneak peek into how their sites with the latest release, but don’t want to take part in the core development cycle, really really should test.
Release candidates are like being given a pre-release. It is stable. It has been tested. Unless YOU find any issues, this will be the next release of WordPress. So get stuck in!
“Less bugs, more polish, the same beta disclaimers.”
Download here: http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/
WordPress 3.3 Release Candidate 2 has hit the ‘net!
Looks like the core team are keeping it hot! Full release expected this side of Christmas!
WordPress 3.3 RC 2
All my seasonal wishes are coming true 🙂