[wp-trac] [WordPress Trac] #10611: Support Partial core upgrades

[WordPress Trac]

#10611: Support Partial core upgrades
-----------------------------+-------------------
 Reporter:  dd32             |       Owner:  dd32
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  3.2
Component:  Upgrade/Install  |     Version:  2.9
 Severity:  normal           |  Resolution:
 Keywords:  featured         |
-----------------------------+-------------------

Comment (by nacin):

 [18224] were changes requested by Jane and also a bug I noticed.

 [18225] was the result of a desire to have an absolute minimum amount of
 code go into core for this feature. Indeed, there are only two changes: A
 new API that delivers serialized responses modeled after the object that
 WordPress used to construct using the newline response (thus minimizing
 the changes required for the upgrader), and a bit of code in the upgrader
 to select which of four packages to download.

 The packages are as follows:
  * '''partial''' - This zip uses the reported $wp_version to deliver an
 in-branch partial zip. If you're on 3.1.x and are upgrading to 3.1.y,
 you'll get something like wordpress-3.1.y-partial-x.zip from the API.
 Partial builds won't be used when you request a re-install. I'm working on
 a separate patch now that will further validate on the core side that the
 right partial build is being used.

  * '''new_bundled''' - This zip has the newest bundled theme. The version
 in which the latest bundled theme was added is also included in the
 response. Core will no longer touch any existing theme, it will only
 deliver a new one, and only if CORE_UPGRADE_SKIP_NEW_BUNDLED isn't set.
 Core will never touch or restore an existing plugin.

  * '''no_content''' - This zip contains no plugins or themes. It will
 however include /languages once the localized build system supports these
 new builds (and until we have language packs, which I'm aiming for 3.3).

  * '''full''' - This zip contains everything. Core should never fall back
 to this once the build process is in place.

 This ticket can be closed as fixed once:
  * The new build process on WP.org is in place, functional, and tested.
 It's important to note that none of this comes into play until 3.2.1, so
 I'm establishing a system to test this on my sandbox. (Beta Tester updates
 rely on nightly builds.)
  * version-check/1.6-beta/ is moved to 1.6.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10611#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software