update-core should be folder agnostic

[wpmuguru]

Currently, update-core is hardcoded to specific base folders in the extracted zip. To support upgrading both WP & MU to 3.0, the base folder should be a parameter to the main upgrade processes.

[ryan]

It shouldn't assume $working_dir/wordpress. For upgrades from MU it can be $working_dir/wordpress-mu.

[ryan]

We can simply check if global $wpmu_version is set and use wordpress-mu if so.

[ryan]

Untested patch. This assumes we change ​http://api.wordpress.org/core/version-check/1.3-mu/ to return a 3.0 package rooted at wordpress-mu.

[ryan]

​http://wordpress.org/nightly-builds/wordpress-mu-latest.zip

[automattor]

(In [15059]) check both wordpress & wordpress-mu roots in update core, see #13625

[ryan]

​http://api.wordpress.org/core/version-check/1.3-mu/?version=3.0-RC1&wpmu_version=3.0-RC1

[ryan]

Someone using MU 2.9.2 or earlier should be able to set $wpmu_version in version.php to 3.0-RC1 and get auto upgraded to the latest nightly. The package should be rooted at wordpress-mu so that is places nicely with 2.9.2.

[wpmuguru]

(In [15061]) remove naughty not, see #13625

[nacin]

Tested and works wonderfully.

We have to make some API changes come release but that's part of the launch checklist.