proposal do disallow syncs of library packages from experimental without approval

Benjamin Drung bdrung at
Wed Oct 5 23:16:05 UTC 2011

Am Mittwoch, den 05.10.2011, 14:35 -0400 schrieb Barry Warsaw:
> On Oct 05, 2011, at 07:07 PM, Stefano Rivera wrote:
> >The sponsors not requesting testing and a transition effort commitment
> >is something I've noticed too. I see transition sync requests that I
> >don't look at immediately because they'll need a fair amount of review,
> >and 10 mins later someone has gleefully sponsored them because they
> >build successfully.
> Maybe we need to find ways to flag such potentially troublesome syncs early in
> the process, so that it's more clear to the developer and/or sponsor.  Have we
> documented a specific set of criteria to watch out for, and can some set of
> checks for those criteria be automated?

Yes, sponsor-patch could compare the old and the new list of binary
package. If this list differs, it should ask the sponsoree to confirm
this change.

Benjamin Drung
Debian & Ubuntu Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the ubuntu-devel mailing list