Can't commit a new release

ricflomag - October 11, 2007 - 17:06
Project:CCK Address Extensions
Version:5.x-1.x-dev
Component:Other
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed
Description

I've been fighting with cvs for more than an hour now but can't manage to release a 1.3 version. I have done what http://drupal.org/handbook/cvs/quickstart explains:

If you later fix additional bugs in this module, you may want to put out a 1.1 release (6.x-1.1)
cd contributions/modules/example
cvs update -dP -r DRUPAL-6--1
# edit some files and fix a bug
cvs commit -m "#54321: Fixing critical security error"
cvs tag DRUPAL-6--1-1

... but when i go to the "add new release" page of the module, i'm only given the choice of the "HEAD" CVS identifier...

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/cck_address... does indeed show the latest files i have committed.

On another hand, the 1.x-dev version is not up-to-date, though this part of the cvs quickstart guide:

In order to allow people to test your module while it is in development, you may wish to make a development snapshot. This will create a "dev" snapshot which will always point to the newest version of the module in a particular branch.

seems to tell that there is nothing to do to have it updated...

In a word, i'm lost ;-) Any thoughts ?

#1

rconstantine - October 11, 2007 - 21:41

I see that for some reason there are actually no branches for the project as a whole other than MAIN/HEAD. I also see that you were able to create a tag for Mexico after I committed Belgium, so it seems you should still be able to do that.

Now, if you are trying to tag the whole project, I'm sure that won't work right now because you would need to download all sub-modules, create a new branch for the whole thing, then tag that as tags can't seemingly come from MAIN/HEAD - at least ti think so.

As for dev, it takes up to 12 hours for the new tar to appear and I see a new one.

So try first to make sure that you're in the Mexico directory when you try to make a new tag.

Um, what are you using for CVS access? If you're using tortoise, I can give you specifics on how to do things.

One other thing I thought of: you have to update your directory to the correct branch before you can tag. I always follow this procedure: (1) update 'special' to the latest HEAD (2) copy my new files over the updated ones (3) commit to HEAD (4) update 'special' to the branch I'm working with (5) copy my new files over the updated ones (6) commit to the branch (7) tag if necessary (8) update 'special' to HEAD so it's ready for next time

The above procedure means that my working directory is not the directory I commit from, otherwise each update would overwrite my new files. I hope this helps. I'll see about creating overall project updates after you figure out how to tag your folder. I'll look here for a report of your success.

#2

rconstantine - October 11, 2007 - 21:43

I should probably have said "update special" not update 'special'. "update special" is the command I use in tortoise to change branch/tag directories and download the latest versions.

#3

ricflomag - October 11, 2007 - 23:19
Status:active» closed

Thank you, i had to move to the Mexico directory indeed. As you can see, i've had some problems releasing my updates (v1.3 did not include Belgium support because i had not tagged its files, and v1.4 contained html files instead of php code because of a weird thing i had done...), but finally here it is.

I'm now using a graphical CVS tool called tkCVS (tortoise is only available on windows i'm afraid), and i believe that i understand how to use it. Doh!

 
 

Drupal is a registered trademark of Dries Buytaert.