Not logged in - Log In / Register

Priorities for the Soyuz Team

Individual Priorities (1 highest) are listed in the columns, otherwise the list is sorted in overall priority order after review.

* M T U Feature Story Points Released
Support for pocket dependencies in PPA
(proper fix for security dependency model)
8 2.1.11
API to copy packages, particularly from the main archive to a PPA, but can be generalised. (bug 276022) 5 2.1.11
1 6 Rebuild integration and UI
Associated with Archive Branches
8 2.2.1 (requires fast slave-scanner)
2 Signed PPAs
13 2.1.12
1 Soyuz ACL manipulation API/tool
Allows ACL manipulation of packages (versus teams) via a distro tool
8 2.1.10
UI for build dependency work to allow user-setting of the build dependency components/pockets 5 2.1.12
11 18 Multiple PPAs per person 5 2.2.4
API manipulation of PPAs (bug 276020) 13 2.2.5
Complete Private PPAs
Management of passwords/security to access P3As
20 2.2.5
Upload handling (ACLs etc) changes for the Archive Reorganisation 2.2.5
Karma for uploads 2 2.2.3
16 280958 Show PPAs containing the same package on Ubuntu package pages. 5 2.2.7
6 Support for handling debug symbol uploads in virtual buildds
8 2.2.7
PPA uploads should be optionally notified to another email address 3
PPA upload permissions should also allow arbitrary 3rd parties 3 2.2.7
External PPA dependencies 3 2.2.7
PPAs should allow partner uploads 0.5 2.2.7
9 14 285205 Handle ddebs in Soyuz 8 2.2.7
JauntyGnomeHelpLangpacks Needs to be ready around Karmic 5 2.2.7
- PPA download counters
Enable the distro team to prioritise merges from PPAs based on real usage and popularity and testing
Could depend on diskless archives, or could be done through log scraping
4 API/UI to unembargo security package
Model through the existing package upload table
8 2.2.7
15 Re-write cron.publish in Python Spec: SoyuzDistributionScript 3
2 7 Provide support for package sync reviews
Consider how critical uploads, bugs, the upload queue and PPAs can interact
3 2 Package sets
Deal with loss of components with the Archive Reorganisation
Deal with loss of components maintenance and support tracking Archive Reorganisation
7 - Licensing Metadata support (see 1 and 2
Extra data on SPR that specifies the set of licenses for a package; obtained by parsing the licensing description and creating a set)
5 8 Changelog repackaging for native source syncing
Allows us to store proper changelogs for Debian-NSS'd packages
5 8 55795, 139162, 247456 Fix changelog attribution and repackaging for native source syncing 5
9 214612 Support PDiff for apt-get update XXX
4 10 285207 Pool buildds between PPAs and the distro 3
8 11 285206 Make buildmaster work with buildds that build any arch 13
12 259422 Display PPA diffs against Ubuntu 5
13 13 235064 Multi-series support in package uploads 8
3 17 Do an emergent "heat" on PPA's, which would quietly factor in downloads, subscribers, karma of uploaders etc. 5
19 SFTP package uploads
Provide a secure upload mechanism with synchronous feedback to uploaders; GPG still a requirement
- Per-package apt:// download links.
20 NoMoreAptFtpArchive (package metadata, speeds up publishing by 20m) 8
13 RealDistroReleases (point-releases)
Depends on 'Archive Branches'
- Archive from librarian (dynamic pool, and autogenerated dists) 20
21 Archive Branches, Snapshot Archives and Independent Suites
(could we have hardy-intel?)
If done with ''Diskless Archives'' makes archive branching cheap
10 - Upload RSS feed
- LiveFS generation
Begin with NoMoreSourcePackages (, data model, branch uploads)
22 Modelling seeds
Data model and basic germinate interface
Could be done with 'NoMoreAptFtpArchive' which needs to know about seeds
Package copying only shows first 20 packages (bug 276019)
- Current SourcePackage metadata persistence
Internal-only, performance and correctness, enables per-package features
- Explicit Distribution.currentseries
Internal-only, perf and correctness

Story cards



     "Private PPAs. We have the following requirements for Private PPAs:
     1 Multiple components in each PPA. We need to deploy closed-source or
       restricted code to the PPA. I want that code to go into multiverse or
       restricted rather than main.
     2 Priority build queue. We can't afford to have PPA builds delayed for
       hours because someone else is building gcc"


VersionThreeDotO/Soyuz (last edited 2009-07-30 10:27:48 by julian-edwards)