WordPress Ideas » Tag: core updates - Recent Posts

Ipstenu (Mika Epstein) on "Updating only the updated files (core)"

Ipstenu (Mika Epstein) — Wed, 27 Jul 2011 17:13:33 +0000

Done as of WP 3.2 :)

Danielx64 on "Updating only the updated files (core)"

Danielx64 — Thu, 10 Feb 2011 03:03:56 +0000

Well I would like to see it happen. The latest update got me suspended by me webhost (x10hosting) because I was using too much RAM and CPU.

Barış Ünver on "Updating only the updated files (core)"

Barış Ünver — Wed, 09 Feb 2011 19:12:40 +0000

As I said, it could be automated (automatted :D).

ucfknight10 on "Updating only the updated files (core)"

ucfknight10 — Wed, 09 Feb 2011 18:30:16 +0000

while i like the idea of only providing the files that have been updated, i think it would create a lot of extra work whenever a new version comes out.

and while download and unpacking would be faster, it's still pretty quick as is.

Barış Ünver on "Updating only the updated files (core)"

Barış Ünver — Tue, 08 Feb 2011 23:53:32 +0000

Core updates are done by the webserver downloading the latest version of WP from wordpress.org (or lang.wordpress.org), unpacked and updated.

I don't think that the webserver should download the whole package. Changed files are easily tracked by Trac. For example:

http://core.trac.wordpress.org/changeset?old_path=tags/3.0.4&new_path=tags/3.0.5

This page contains a list of changed files between the two versions and if that list could be generated, zip files with the files in the list should also be generated (e.g. wp-3.0.4to3.0.5.zip or wp-3.0.1to3.0.5-tr_TR.zip).

This should increase the performance during core updates. Smaller files would be downloaded quicker, unpacked quicker and updated quicker. Right?

PS: Please don't say that "you should create an issue on Trac", I really tried but couldn't understand how that system works :)