Leaving the SRU team due to OEM rotation

[Martin Pitt]

John Dong [2010-04-21 18:02 -0400]:
> This seems to be the root of some level of confusion when the
> ubuntu-sru and motu-sru teams merged. Traditionally, the motu-sru
> procedure asked for debdiffs to be reviewed and ACKed before the
> upload is performed, while the ubuntu-sru procedure reviews the
> patch after it has been uploaded. 

I think we still have to do both, since we only suggest, not mandate,
that people upload proposed packages before the review (to speed up
the process, and based on the experience that most uploads are ok).

> I don't want to be the one to insert unnecessary bureaucratic
> systems into the SRU procedure

Let's first figure out whether it's necessary. :-) If there's an
improvement which would help you, please by all means do it.

> However, if I needed to quickly know "are there any SRU bugs that
> need my attention?", I don't have a quicker way than grabbing a
> coffee and going through my SRU bugs folder. The security team seems
> to have a nice table (forgot the link) of all the CVEs and their
> status in various Ubuntu branches -- it'd be awesome if there's a
> Launchpad query or something that could generate a SRU radar screen.

There's always
https://bugs.launchpad.net/~ubuntu-sru/+subscribedbugs?orderby=-date_last_updated

but currently there are 490 open bug tasks where ubuntu-sru is
subscribed, so before that list can be really useful we'd need to do a
major cleanup (some are tricky -- e. g. there are a ton of open linux
bugs which were fixed in SRUs, but never closed in the devel release :-( )