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!
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!
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!
1. Go to your project page. 2. Find where it says you can download the "2.x-dev" release. 3. Click on the "edit" link to the right (which should be visible if you are the maintainer). 4. Change the CVS version this comes from and save. Or click delete if you don't want the 2.x-dev version to be available for download from the project page. Then you can go ahead and create a new release called 3.x-dev and point it to head. I think this will fix what you were orginally asking about... --Jennifer
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?
-- Jennifer Hodgdon * Poplar ProductivityWare www.poplarware.com Drupal, WordPress, and custom Web programming
On Thursday 06 May 2010, David Cohen wrote:
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?
I'm having the same problem, two 1.x-dev tarballs. I've got around it by not enabling snapshots. Creating a new branch DRUPAL-6--2 has not resolved the issue. I have followed Jennifer's advice but no edit button, I am the (only) maintainer. Hopefully this will be resolved with the implementation of git.
-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!
-- ----------------- Bob Hutchinson Midwales dot com -----------------
Bob Hutchinson wrote:
On Thursday 06 May 2010, David Cohen wrote:
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?
I'm having the same problem, two 1.x-dev tarballs. I've got around it by not enabling snapshots. Creating a new branch DRUPAL-6--2 has not resolved the issue. I have followed Jennifer's advice but no edit button, I am the (only) maintainer.
Hopefully this will be resolved with the implementation of git.
This is beginning to sound like a bug in the project module driving d.o/project. There should be no method to allow you to have two -dev versions of the same branch tag listed on the modules project page. -- Earnie -- http://progw.com -- http://www.for-my-kids.com
David Cohen wrote:
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?
I tend to match HEAD to the latest revision before creating the branch for the next Drupal major version. But only to help control the CVS revision numbering. So I'll update head with the latest code from the 6.x branch and then make my 7.x branch from it. All other branches come from the newly created branch. In essence the branch for the Drupal major version becomes the HEAD for the Drupal release. -- Earnie -- http://progw.com -- http://www.for-my-kids.com
At the time you create a new branch in CVS, e.g., DRUPAL-6--3, you should be able to edit the existing development snapshot that is currently pointing to HEAD, and change it to point to the new DRUPAL-6--3 branch instead. This, however, only works when there is no dev snapshot for DRUPAL-6--3 yet. Afterwards, you can create a new dev snapshot pointing to HEAD, i.e., for 4.x-dev. sun
-----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of David Cohen Sent: Thursday, May 06, 2010 1:17 AM To: development@drupal.org Subject: Re: [development] dev release of contrib module using CVS HEAD
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!
participants (6)
-
Bob Hutchinson -
Daniel F. Kudwien -
David Cohen -
Earnie Boyd -
Jennifer Hodgdon -
nan wich