1

Whenever I go to create a release for my contrib module, it gives me one option - 6.x-1.x (6.x-1.x-dev) - but if I select that it says "The version you have selected (6.x-1.x-dev) is already in use by another release." IIRC dev releases are packaged automatically every twelve hours, so why is this option even appearing? And it seems like dev releases aren't being packaged automatically for my module ...

  • Are you seeing the commits show up on the Revisions tab on the project? – mpdonadio Jun 11 '13 at 23:15
  • See my comment below: I would have thought that the commit at drupalcode.org/project/csm.git/commit/b2b9979 would have triggered a new dev release, but it didn't – Jim Jun 12 '13 at 18:32
2

In the "Release" tab of your project you've a checkbox with "Show snapshot release". If you check it, you should see the dev releases appear.

  • Thanks, @yvan. That box is already checked, though. Dev releases were appearing until January this year, but not any more for the 6.x branch (and there's been a full release on that branch since then, which is appearing fine) – Jim Jun 11 '13 at 22:11
  • Well have you made any commits since January? The dev release is automatically regenerated each day if there are new commits. – Bojan Zivanovic Jun 12 '13 at 9:23
  • I would have that that this commit - drupalcode.org/project/csm.git/commit/b2b9979 - would have triggered a new dev release, but it didn't – Jim Jun 12 '13 at 18:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.