If the XML history files generated by project-release-history.php included the same CVS branch/tag info that the release nodes do, then the CVS deploy module could be even smarter. If it sees you're running HEAD or another branch, instead of a specific release tag, it could search the release history for that branch and use the real version string of the dev snapshot release node pointing to that branch. This would a) give better results for folks checking out from HEAD and b) protect us from printing the wrong thing in the case of DRUPAL-5 branch, which some people incorrectly use for later release series, instead of just leaving that for the 5.x-1.* series (see http://drupal.org/node/147493 for fixing that for the future).

Once this server-side change is done, I'll roll a patch for cvs_deploy.module to use it (if update_status.module is enabled).

CommentFileSizeAuthor
project-release-history-tag.patch.txt1.49 KBdww
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

+1 for carrying the CVS tag to the release history.

webchick’s picture

Status: Needs review » Reviewed & tested by the community

Works for me. Logical, and doesn't seem to adversely impact performance or anything.

dww’s picture

Status: Reviewed & tested by the community » Fixed

committed to HEAD, installed on d.o, and re-running the history generation script right now to produce the new .xml files...

see http://drupal.org/node/152387 about the corresponding feature request for CVS deploy to take advantage of this.

Anonymous’s picture

Status: Fixed » Closed (fixed)