Milestone and release URLs confusing

Bug #374671 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Now that there is a unified page to show a release with its milestone, there are two ways to traverse to milestones - /<product>/<series>/<milestone> and /<product>/+milestones/<milestone>. Although the +index is identical, the other views are not, and the former traversal method only works when a release exists for the milestone.

Now that the namespace is unified, why not drop the +milestones from the path and change the traversal to releases to something like /<product>/<series>/<milestone>/+release?

Revision history for this message
Curtis Hovey (sinzui) wrote :

I think this is out intent. Well it is my intent, I have not gotten agreement yet.

Note that we support /<product>/+releasess/<release>, but we do not make any links to it. I discovered this is/was broken for several months because we are missing test coverage (I did fix the problem)

I think we want to just make links to /<product>/<series>/<milestone> from now on.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I am hesitantly scheduling this for 2.5. I certainly hope to achieve must of this by fixing other parts of the UI. I am not certain all the work will be complete though.

Changed in launchpad-registry:
importance: Undecided → Low
milestone: none → 2.2.5
status: New → Triaged
assignee: nobody → Curtis Hovey (sinzui)
Curtis Hovey (sinzui)
tags: added: story-series-milestones-releases
Revision history for this message
Curtis Hovey (sinzui) wrote :

Changing the milestone URL to the same as the release URL will break the beta API. Code that expects a release will get a milestone. The code could be adapted to only return a milestone if a release does not exist, but that idea hinges on the insane.

Revision history for this message
William Grant (wgrant) wrote : Re: [Bug 374671] Re: Milestone and release URLs confusing

On Wed, 2009-05-13 at 19:02 +0000, Curtis Hovey wrote:
> Changing the milestone URL to the same as the release URL will break the
> beta API. Code that expects a release will get a milestone. The code
> could be adapted to only return a milestone if a release does not exist,
> but that idea hinges on the insane.

Isn't during the beta the best time to break API compatibility?
Otherwise you'll never be able to fix this.

--
William Grant

Curtis Hovey (sinzui)
Changed in launchpad-registry:
milestone: 2.2.5 → 2.2.6
Revision history for this message
Curtis Hovey (sinzui) wrote :

I would like to do this, but we cannot undertake this change until the traversal rules with the DistributionArchitectureSeries are reconciled.

The series URL is very inconsistent. distro series have an architecture
    <distro>/<series>/<architecture>
and project series have a release.

There is discussion about changing this URL for Launchpad 4.0, so that would be the time to argue for the milestone url change.

Changed in launchpad-registry:
assignee: Curtis Hovey (sinzui) → nobody
milestone: 2.2.6 → none
Curtis Hovey (sinzui)
tags: added: planning
removed: story-series-milestones-releases
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.