SRU policy for universe

Emmet Hikory emmet.hikory at
Wed Nov 21 13:09:55 GMT 2007

On Nov 21, 2007 9:52 PM, Stefan Potyra wrote:
> My current idea to get the universe SRU policy in shape is to basically switch
> back to the old policy, and reuse the motu-sru team for this (with new
> members). To be aligned with main semantics of proposed from main, checking
> of proposals should happen before packages get uploaded to proposed. In order
> to avoid bottlenecks, we could reduce the number of needed acks to one. Where
> someone from the motu-sru team is unsure, he/she could of course state the
> doubts and ask for input from other members.

    This seems relatively sane to me: having team members who review
the debdiffs, any of whom can ACK and upload to proposed.  Perhaps a
"Confirmed" state indicates it needs review, "Fix Committed" means it
needs -proposed testing, and "Fix Released" means it is in -updates.
I'd encourage a larger team, maybe 5-10 people who all currently
active and have a reasonably high count of recent SRU uploads (and so
would be expected to be familiar with the concerns & procedures).

    The archive admins would be expected to confirm that the upload
bug received the necessary ACK, and apply to the archives, rather than
being expected to review the actual changes.

    The universe sponsors would be expected to subscribe ~motu-sru
with an ACK comment if they felt a given SRU candidate was adequate,
rather than uploading to -proposed.


More information about the ubuntu-devel mailing list