Overview

• Launchpad entry: https://blueprints.edge.launchpad.net/soyuz/+spec/soyuz-package-ui

• Created: 2009-06-25 by MichaelNelson

• Contributors:

• Depends on: n/a

Overall Summary

Summary: We will provide an easy-to-use, user interface to represent distribution packages, allowing the viewer to drill-down to more specific information when required.

Goal/Deliverables:

Intuitively rework all the functionality of the various package pages into:

• /distribution/+source/packagename
• /distribution/+source/packagename/version
• /distribution/series/+source/packagename (*)

We will know we have finished when...

All the use cases for viewing GEdit source and binary packages in Ubuntu are accommodated via:

• /ubuntu/+source/gedit
• /ubuntu/+source/gedit/1.2.3
• /ubuntu/karmic/+source/gedit (*)

and the following urls are no longer required:

• /ubuntu/karmic/+source/gedit/version
• /ubuntu/karmic/+package/gedit
• /ubuntu/karmic/i386/gedit
• /ubuntu/karmic/i386/gedit/version

(see whiteboard sketch of the changed URLs from the Soyuz UI sprint)

* I know there was a reason why the distro-series source package view still needed to be separate (ie. some functionality could not be integrated into the distribution source package page), but I cannot remember what it was?

• -- Perhaps it was something to do with source package branches? We have a branch listing hooked off the distroseries source package view at the moment. -- JonathanLange 2009-07-31

Release Note

Rationale

Currently all the various package-related database models, such as:

• DistributionSourcePackage,

• DistorSeriesSourcePackageRelease,

• DistroSeriesBinaryPackage,

• DistroArchSeriesBinaryPackage,

• DistroArchSeriesBinaryPackageRelease, etc.

are all accessed in LP via unique URLs, which results in many different pages all with further details related to the original DistributionSourcePackage.

TBD. Currently just adding this wiki page to attach mock-ups from sprint.

Use cases

Cases that will fail with the proposed URLs

• William, an Ubuntu developer, wishes to see the history of a DAS' binary package releases with a particular name - even those from different source packages. He goes to some page (probably still DASBP), and sees a full history.
  • [Julian] The new search page searches binaries but presents sources related to that binary. Perhaps we can tweak that page to accommodate?

Assumptions

User Interface

Implementation

Code Changes

Schema Changes

Migration

Unresolved issues

In this section list out any issues which are unresolved and will impact or block the implementation of this spec.