On Wed, Apr 10, 2019 at 7:21 AM Matthias Klose <[email protected]> wrote: > > Please can we delegate the hinting for autopkg test failures to core > developers > and MOTU?
Hi Matthias, I like the idea, but to be specific I assume you only refer to the hinting done in the current dev release. Changes to hinting for released versions should stay with the SRU Team only right? > When ignoring an autopkg test failure, you usually have a reason to do so. > As a > core developer you already can work around autopkg test failures with > uploading > a work-around in a new package version, both for main and universe packages. > The disadvantage is a longer turn-around, re-triggered autopkg tests, > introducing a delta which has to be maintained. MOTU could be limited to only > hint failures for universe packages. > > The current limitation of autopkg related hints being done by the release team > seems to be a technical limitation, because other hints are done by the > release > team only. Of course there should be informal restrictions for hinting during > archive freezes, release freezes. /me has removed a lot of suggestions how to implement things I tried to write as answer at first. I think we need to focus on discussing what we'd want before we go into how to achieve that. Therefore lets see what the discussion brings, as all of this is a bit mix-and-match depending on preferences. Personally I'd appreciate something staged like: A/B depending on how much we want to trust each other :-) A) - overrides to main stay with the release team - overrides to universe can be committed by core-devs (keep some formal checking) B) - overrides to main can be committed by core-devs - overrides to universe can be committed by MOTUs -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
