Hi,
I posted this in the Drupal Module Development forum, where it dropped to the second page in about 24 hours. It occurred to me, after attending the recent Drupal Camp, that we have a lot of Drupal experts right here in Portland. So if anyone knows the answer to this question, I would appreciate the help. You can post a reply here or at http://drupal.org/node/273520. Thanks!
My first ever Drupal module is at http://drupal.org/project/uc_addresses. I think I screwed up the releases and I would like to get them as close to "Drupal-standard form" as possible.
First, I created a branch for Drupal 5. I then created the developer release. When it asked me for the CVS identifier, I picked the Drupal 5 branch. After all, I should be able to create a developer build for the Drupal 5 and a separate one for Drupal 6, so I figured I needed to tell the system which branch to use. I entered major release 1, patch-level x, and extra identifier "dev".
I then dropped a tag for an RC1 release and created the corresponding rc1 release.
I assumed that the developer release was automatically rebuilt any time the head of the corresponding branch changed. Eventually, I discovered that the developer release hasn't been rebuilt since I first created it. I can't delete this release, nor can I re-assign it to HEAD, nor do I know how to force a rebuild.
So, masters of CVS, what should I do so that the developer release always contains the latest code for the Drupal 5 branch of my module?
Comments
looking at your commits it
looking at your commits it looks like you're working on HEAD rather than the DRUPAL-5 branch you created. this means that your commits and tags are being created on the HEAD "branch". if the -dev release is on the DRUPAL-5 branch you won't be seeing those and won't get updated -dev releases packaged.
i don't create a branch until i've finished the whole -beta1 -beta2 -rc1 cycle and then create the DRUPAL-5--1 branch (you could create a DRUPAL-5 branch but in 6 you can't create DRUPAL-6 it's got to be DRUPAL-6--1 so I'd just start using the new system). That way the 1.x branch is your stable code and you only commit bug fixes. You keep committing new features to HEAD and when you get it where you like it create a DRUPAL-5--2 branch. Eventually you start working on 6 and tag HEAD with with the DRUPAL-6--1-0-beta tags and finally create a DRUPAL-6--1 branch when it's ready.
Thanks!
OK, I think I see. I went back to the Drupal CVS handbook and I see that the wording can be misinterpreted if not read carefully. The "dev" version comes after the first release, not during "development". You can understand how this could be confusing.
I think I'll need to make a Drupal support request to get this straightened out. Thanks for explaining the problem.
Tony Freixas
tony@tigerheron.com
http://www.tigerheron.com
Tony Freixas
tony@tigerheron.com
http://www.tigerheron.com
actually you can use it
actually you can use it either way, because the -dev release is really just what ever is at the end of the branch. and you created one on one branch and were committing to another. that's why i don't branch until after i've release because otherwise you've got to commit your patches twice, once on the HEAD branch and again on the stable branch.