Verify updates with md5 checks
|Reported by:||nacin||Owned by:||dd32|
|Cc:||sbressler@…, chacha102, mike@…, dempsey@…|
Before an update, we should verify core files with a list of md5s, returned through the API. We should do this in order to determine whether we can safely do a partial build, or if we should just copy over everything.
During the update, we can avoid copying over any files that are up to date, as verified by md5 results beforehand. This should save a number of FTP calls, in particular.
After the update, we should md5 files we've copied over, and see if anything went wrong, and try again if necessary. Unfortunately we don't always know why updates fail, so we're going to need to test the hell out of this and see what kinds of cases we can cover. (Maybe it's time for error reporting back to WP.org?)
Any other thoughts?
Change History (40)
- Milestone changed from 3.3 to Future Release
- Priority changed from normal to low
- Type changed from task (blessed) to feature request
comment:24 dd32 — 3 months ago
- Owner set to dd32
- Resolution set to fixed
- Status changed from new to closed