update_status 5.x-2.1

This release fixes some critical bugs and includes the final changes to the update.module that is now part of Drupal core 6.x.

Please note that the API between Update status and the CVS deploy module has changed with this release. Any sites that are deploying Drupal modules via CVS that wish to use this release must upgrade to CVS deploy version 5.x-1.1.

Bugs fixed since version 5.x-2.0:

• #208687 by dww: Fixed major bug that printed bogus results and recommended that users downgrade to an older version when a site upgraded a module or Drupal core but did not manually refresh the available update data. Now, before using the cached available update data, the code ensures that none of the .info files have been changed since the last time it fetched data.
• #197186 by dww: Backport of major update.module patch from D6 core:
  • Fixed bug where update_status would not warn sites when a currently installed release or an entire project being used has been unpublished.
  • Added support for project maintainers that want to support multiple major versions (branches) for one version of core.
  • Added support for flagging both individual releases and projects as "unsupported" or "insecure", to pave the way for new workflows (instead of just unpublishing things) for the Drupal security team and project maintainers.
  • Reorganized and simplified some code to avoid duplication and needless complications.
• #184900 by webernet: Fixed bug where email wasn't getting sent in some cases when it should have been.
• #196775 by dww: Fixed a bug that caused truncated error messages to be displayed when the site is running an insecure version of core.
• #168352: Fixed small typo in settings description text.

Other changes since version 5.x-2.0:

• #200028 by agentrickard, dww: Significantly enhanced performance of the admin/* pages by adding DB caching for the list of installed modules and their current status. The cache is cleared every time new available release data is fetched, every time the admin visits the modules page, status report, or available updates report, or every hour if nothing else clears it before that.
• #158526 by dww: Changed the hook_version_alter() API exposed by update_status to be hook_system_info_alter() so that all attributes in the .info files can be altered. This API change is required to fix some bugs in the http://drupal.org/cvs_deploy module, which is the only known user of this API.
• #178892 by webchick: Use an API function to get the private key.
• #212813 by dww: Project status information on the status report is now linked to the admin/logs/updates page (usability enhancement).
• #211403 by dww: Removed fallback code for determining the project based on the directory. This code only matters if you deploy from CVS, and doesn't work if you install into subdirectories of the 'modules' folder (for example, sites/all/modules/contrib/foo). For cvs_deploy to fix this problem (#184664) correctly, the heuristic code here must go.
• #168828 by dww: Added note to README.txt about the requirement that httpd needs to be able to initiate outbound network connections.