Persist information for sourcepackage publication metadata
Bug #236922 reported by
Christian Reis
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
To avoid expensive publishing-related queries when fetching publication metadata, such as the current package's component, we should find a way to persist this information in the database.
Revision history for this message
| Christian Reis (kiko) wrote | #1 |
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: soyuz-core soyuz-publish |
To post a comment you must log in.
Part of what we'd like to do here is encode the idea of a "current" package. When a person comes in and look at xchat in Ubuntu, what version does it make the most sense for us to be highlighting?
For developers it's almost definitely the version in the latest development release.
For end-users it might vary.
Most of our use cases for Soyuz and Malone are centered around developers.