milestone versioning logic does not align with debian
Bug #1084436 reported by
James Hunt
This bug report is a duplicate of:
Bug #581748: 10.10 milestone name corrupted in JS: 10.1.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
If you attempt to create a milestone '0.10' where you already have a milestone '0.1', launchpad will refuse claiming that you have already created a '0.1' milestone.
This diverges from expectations:
$ dpkg --compare-versions 0.10 gt 0.1 && echo '0.10 is greater than 0.1'
0.10 is greater than 0.1
To circumvent this, I had to create a 'v0.10' milestone for the project below, but that plays havoc with the milestone graph as you'll see:
Revision history for this message
| William Grant (wgrant) wrote | #1 |
To post a comment you must log in.
This is a known bug in some of the old AJAX infrastructure; it ends up treating it as a float, so a trailing 0 disappears. You can rename the milestones to the correct version from the "Change details" link on the milestone page.