[drupal-devel] Re: Help?

Gabor Hojtsy gabor at hojtsy.hu
Wed Apr 6 14:22:44 UTC 2005

>> The latest release date is based on when the branch was created, not 
>> when something was last committed.
> I understand that. That's the problem. I want the current version of the 
> module to be what people get when they click on the link that says 
> "download latest release." Right now they're getting an old version. How 
> do I fix that?

If you already branched your module for 4.5, the best you can do is to 
do your changes in the 4.5 and in the HEAD branch, if you think your 
changes should go to the head branch too. The type of cvs commit 
messages you see indicate this type of workflow:

HEAD commit message:

  - updated foo to be correct

DRUPAL-4-5 commit message

  - updated foo to be correct (backported from HEAD)

If you retag your module (ie. move your tag around), it will be harder 
to check out the changes you made to that branch, since the branch 
starting point will be moved, and we will not be able to see the changes 
you made to that branch.

Check my january 7 commits here:


This way one can see how that README.txt evolved over time in the branches:


If I would have moved the release tag, or the branch starting point, 
noone would be able to tell that I changed something in the release.


More information about the drupal-devel mailing list