launchpad considers milestone "1.10" the same as "1.1"
Bug #1215983 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 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm trying to release Upstart 1.10 (the version after 1.9), but attempting to create a milestone called "1.10" gives the error:
name: The name 1.1 is already used by a milestone in upstart.
This is nasty as the expectation is that launchpad has the same version logic as "dpkg --compare-
I have previously hit this issue and thought I'd filed a bug but cannot now find it. My last attempt at a work-around "worked" (I started pre-pending 'v' for version, but the results are confusing to say the least:
https:/
The work-around I'm using today is to create the milestone as "1.10.0" but this is potentially confusing to users since the release is called "1.10".
To post a comment you must log in.
