Closed (duplicate)
Project:
Git on Drupal.org
Component:
Releases
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Jul 2011 at 21:46 UTC
Updated:
9 Aug 2011 at 19:30 UTC
I tried to make a new release 6.x-1.1 by tagging 6.x-1.1 to a current 6.x-1.x (6.x-1.x-dev). However, when I tried to do "Add new release" and "Create Project release" (see a screen shot), the release page says: "The version you have selected (6.x-1.1) is already in use by another release." Then I clicked "another release" link, it goes to 6.x-1.01 release page. I am not sure what is happening here.
Are the release of 6.x-1.1 and 6.x-1.01 recognized as the same release? Should I need to tag 6.x-1.2 if we have 6.x-1.01 release? Or, is there some way around to break a relationship in between 6.x-1.01 and 6.x-1.x? Please advise me about it.
| Comment | File | Size | Author |
|---|---|---|---|
| screenshot 20110703b.png | 117.91 KB | yas | |
| screenshot 20110703a.png | 121.62 KB | yas |
Comments
Comment #1
danielb commentedI don't think '01' goes with the tag naming convention.
Comment #2
dwwSee #1226074: Disallow leading zeros in git tag/branch validation for the real solution to this. We should never have let you create a release from a "6.x-1.01" tag in the first place.