If I get what you're saying, I can create the DRUPAL-6--3 branch, then when the time comes create the DRUPAL-6--4 branch off of that, and so on. It will have a bizarre effect on the version numbers, making them unnecessarily long, but I guess most people wont notice that. And the HEAD branch will just be left as is till the end of time (or end of drupal cvs which will hopefully be soon). But even still, there is now a 2.x dev release being created from the HEAD branch which conflicts with the DRUPAL-6--2 branch, and I have no way to prevent that release (HEAD) from being built. I can't be the only one to have encountered this. How do other contrib developers deal with it? -Dave On Wed, 05 May 2010 10:49 -0700, "nan wich" <nan_wich@bellsouth.net> wrote:
I'm sure Derek will correct me if I am wrong. You should go ahead and create the DRUPAL-6--3 branch (but no tags), then the -dev from HEAD will go to that. Nancy E. Wichmann, PMP Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
________________________________ From: David Cohen <drupal@dave-cohen.com> To: development@drupal.org Sent: Wed, May 5, 2010 12:48:28 PM Subject: [development] dev release of contrib module using CVS HEAD
I maintain a contrib module with multiple branches in drupal.org CVS.
Until recently, my HEAD branch corresponded to the 2.x release.
Now, I've created a DRUPAL-6--2 branch for the 2.x release. HEAD is now 3.x.
My problem is that drupal.org gives me no way to change the version associated with the HEAD branch. Right now, my project page offers two releases both called "6.x-2.x-dev". One of those should be 6.x-3.x-dev. How can I change it?
(Replies should probably go to this forum post: http://drupal.org/node/789978)
Thanks!