cvs_deploy 5.x-1.1
Official release from CVS tag: DRUPAL-5--1-1
Download: cvs_deploy-5.x-1.1.tar.gz
Size: 8.72 KB
md5_file hash: 5c76bbfd650502f7fd1c72e55bba8278
First released: January 30, 2008 - 18:51
Last updated: January 30, 2008 - 18:55
Download: cvs_deploy-5.x-1.1.tar.gz
Size: 8.72 KB
md5_file hash: 5c76bbfd650502f7fd1c72e55bba8278
First released: January 30, 2008 - 18:51
Last updated: January 30, 2008 - 18:55
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.
