The nice auto-plugin-update feature doesn't work in mu because mu's schema.php explicitly disables the new update_plugins and delete_plugins admin capabilities.
Why? Is there something dangerous about allowing the mu site admin to update and delete plugins?
Even if it required temporarily downing the sites, that feature is very nice.
Most folks test first before installing new features or upgrades to make sure things work correctly. Also there's no guarantee that a newly upgraded plugin will be secure.
Many plugins require some sort of fix or rewrite to work with mu as well.
"because mu's schema.php explicitly disables the new update_plugins and delete_plugins admin capabilities."
By admin in that case they means each *blog* admin, and you sure don't want your users to do that.
That's all true. Seems overkill to completely prohibit it however.
For example,
a) in our environment, we have one site for testing and another for production. for plugins that work nicely, it is just handy to be able to do the updates.
b) pre-production, using auto-update is by far the nicest way to ensure everything is up to date before beginning the test cycle...
I'm about to try unlocking...
