Releases for CVS deploy

This is the initial stable release compatible with Drupal core 6.x. Sites deploying Drupal from CVS are encouraged to use this release to ensure that the Update status module included in core will function properly. In addition to all required changes to port to the 6.x API (in particular, the 6.x version of Update status), this release contains all the bug fixes and changes made in the 5.x series up to and including version 5.x-1.1. Finally, the following changes were made specifically for this release:

• #208966: Removed a hard-coded version string that was accidentally committed.
• #221278: Updated README to mention 6.x core instead of 5.x update_status.

This release is required for all sites running Update status version 5.x-2.1, since the API between these two modules is now different. This release is incompatible with Update status version 5.x-2.0, but that release is now deprecated, and sites are urged to upgrade both modules. Changes since CVS deploy version 5.x-1.0:

• #158526: Added better support for deploying from the end of a branch (equivalent to using a -dev snapshot release) by finding the latest modification time on all the CVS/Entries files in a given project and using that value for the 'datestamp' .info file attribute (used by update_status to compare dates for -dev release to see if the site needs an update).
• #211259: When altering the .info array for a given project, also use the most recently modified CVS/Entries file for the '_info_file_ctime' field (to know when to flush the cache of available updates (see #208687 for more information)).
• #184664 by dww: Added support to discover the correct 'project' attribute for modules based on the CVS/Repository file. This fixed a bug in update_status when you install into subdirectories of the 'modules' folder (for example, sites/all/modules/contrib/foo).
• #213014 by dww: Fixed bug in resolving 'HEAD' versions that was caused by using an empty project name when looking up releases in the cached data of available updates from the update_status module.

Official stable release compatible with Update status version 5.x-2.0. Only a few minor bugs have been fixed since the 5.x-1.0-beta release:

• #162737: Fixed bug on modules page confirm form caused by blindly adding the human-readable version strings to the form, even if it's just the confirm form and there's no table of modules.
• #172458: Modified code to explicitly check for the 5.x-2.* versions of update_status functions we want, so cvs_deploy will gracefully degrade if update_status version 5.x-1.* is still in use.

HEAD is currently compatible with the 6.x Drupal core API. This branch will probably undergo many changes as the Update status module moves into core, but the basic functionality is now working.

Initial official release that is integrated with Update status 5.x-2.0-beta.