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
