[wp-hackers] Upgrade sanity checks

[Matt Mullenweg]

Otto wrote:
> One way would be to have it load some other file which is a list of
> all the WordPress files, then check (and potentially hash) them all to
> ensure that they are unchanged. Every time a new release occurred,
> that file would need to be generated as part of the release process.
> Of course, you would want a failure to not *stop* the upgrade, but to
> get confirmation. The best user experience would be to put up a
> warning message saying "These WordPress files don't appear to be the
> correct versions: (list of files here). Proceed with upgrade anyway?
> WARNING: Proceeding may cause unexpected results! Do not proceed
> without knowing what you're doing. (Proceed / For the love of god
> stop!)"

I think that's a great idea.

-- 
Matt Mullenweg
http://ma.tt | http://automattic.com