On Nov 17, 2009, at 7:51 AM, Otto wrote: > Gene, > > There's no way to test compatibility automatically. Provably > impossible. All WordPress could possibly test on an automated basis is > that it loads and doesn't cause a fatal error (WordPress itself does > that on plugin activation). > > Real "compatibility" is only determined by usage. Does the plugin do > what it's supposed to? Which features are broken? But this is a > judgment call, not something you can automate. > > Compatibility is therefore determined by users testing it. The Extend > pages have that box on there to let people say whether it's compatible > with new releases. There's no "2.9" listed because WordPress 2.9 does > not exist yet. This is a BETA release. Things are expected to not > work. Having people report plugin compatibility on those pages with > beta releases is unfair to the plugin authors. If you find > incompatibilities in a Beta release, you should be either contacting > the plugin author about it, or finding a new plugin to replace that > one you're using. > > Anyway, if you want to test your plugins early, go ahead. If not, > don't. And if you're unhappy with that, then don't upgrade until other > people test the plugins for you. Or hire somebody. Or just don't > upgrade. > These are your choices. > > -Otto > Sent from Memphis, TN, United States > ______________________________
OK, let's summarize: 1. scribu's statement that "we have an automated tool for that now on Extend" is wrong based on what everyone else says. 2. Although there was a plugin compatibility page for previous versions of WordPress while they were under development, there won't be one for 2.9? Am I taking your statement as accurate here? Why the change? 3. I understand that in a beta test, you're on your own. Don't patronize me! I was probably beta testing products before you were born. Peace, Gene _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
