Publishing history has only distribution series codenames, not version numbers

Bug #185328 reported by Matthew Paul Thomas
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The "Overview" page for a distribution package (such as <https://launchpad.net/ubuntu/+source/gdm>), and the "Publishing history" page (such as <https://launchpad.net/ubuntu/+source/gdm/+publishinghistory>), list which version(s) of the package was published in each distribution series.

Unfortunately they do this only by giving the series codename (e.g. "Dapper", "Breezy"), not the version number. This is appropriate for development versions, but inappropriate for versions that have already been released, because people new to the distribution are unlikely to be familiar with past codenames.

Revision history for this message
Dennis Schridde (devurandom) wrote :

PS: This is also true for the "Link to other package" action on the release-series page.

Changed in launchpad:
status: New → Confirmed
Curtis Hovey (sinzui)
affects: launchpad-foundations → soyuz
Revision history for this message
Julian Edwards (julian-edwards) wrote :

The overview page now uses a distribution series's "displayname" property instead, which is settable by the distro owner and is the preferred way of someone branding their distro series.

The publishing history is a different matter, since putting the displayname where it currently just shows the name would look terrible. I suggest we do something like:

    9.10 (karmic)
    9.04 (jaunty)

I don't really like the idea of changing what's displayed based on the series status and it's fair to say that different people are more familiar with the name and version.

tags: added: trivial ui
Changed in soyuz:
status: Confirmed → Triaged
importance: Undecided → Low
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Having re-read my last sentence I'll clarify it:

Some people are more familiar with the code name, and others are more familiar with the version.

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.