Readjusting SRU review process

Martin Pitt martin.pitt at
Mon May 13 21:18:01 UTC 2013

Hello SRU team,

the Tech board recently received a proposal to forego the review of
-proposed uploads and directly accept them into -proposed:

In today's TB meeting there was unanimous agreement that this is not a
flaw in the defined SRU process, but a flaw in its execution. We do
not want to give up peer review for what goes into stable releases,
and rather want to address the workflow problem in the SRU team. Does
that match your feeling as well, or do you feel differently?

There are obviously problems with getting timely reviews at the
moment: many items in the precise and quantal queue are one to two
months old already, and even raring's queue has rather simple SRUs
which are already three weeks old.

It seems the regular reviewing days got dropped some time ago. How is
the reviewing process currently meant to work, and what do you see as
the reasons that it doesn't? Would reintroducing regular review days
help against them never turning into your focus otherwise, or have
they been ineffective as well? Mabye the team is even too big now for
anyone to feel sufficient responsibility for doing reviews?

Please don't consider this as personal criticism; we just need to
figure out a modus that actually works.

Thank you!

Martin Pitt                        |
Ubuntu Developer (  | Debian Developer  (
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <>

More information about the technical-board mailing list