Milestone names/version are required to be unique to a project (but users think of them as unique to series)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
It is common for projects to have simple milestone names/version like beta, or 0.1 because they belong to the series. So firefox 3.5 series will have a beta milestone.
Launchpad does not permit this. It requires that the milestone have a milestone name/version that is unique to the project, (3.5.beta) so that project-groups can have a heuristic method to guess milestones that are common to many projects regardless of series.
This causes organisational problems for most projects since most projects are not members of a project group. This causes data problems for tools that mirror projects like the project release finder, which knows how to find releases for a series, but must add the matching files to a milestone in another series. This is a bad experience for working with upstream projects.
tags: |
added: planning removed: story-series-milestones-releases |
tags: | added: linaro |
Changed in launchpad: | |
assignee: | nobody → Данило Шеган (danilo) |
Changed in launchpad: | |
status: | Triaged → In Progress |
Changed in launchpad: | |
status: | In Progress → Triaged |
Changed in launchpad: | |
status: | Triaged → In Progress |
Changed in launchpad: | |
status: | In Progress → Triaged |
assignee: | Данило Шеган (danilo) → nobody |
Changed in launchpad: | |
assignee: | nobody → Brad Crittenden (bac) |
status: | Triaged → In Progress |
Changed in launchpad: | |
assignee: | nobody → Brad Crittenden (bac) |
status: | Triaged → In Progress |
tags: | removed: escalated |
Changed in launchpad: | |
importance: | Critical → High |
status: | In Progress → Triaged |
tags: | added: milestones releases |
Escalated by James Westby for Linaro.