Hello, On Tue 27 Sep 2022 at 09:23AM +01, Matthew Vernon wrote:
> As Sean says, though, questions of what are and aren't RC bugs are typically > the domain of the release team, not the TC. I didn't intend to say that -- I think that Policy+TC decides bug severities, in general. But the RT decide which ones actually count for an impeding release. (One might then argue that that means that the RT do in fact determine which are the RC bugs, but I think that unhelpfully simplifies how Debian decision-making works.) > I don't think you're asking us to revisit our decision on the approach > taken to merged-/usr; we don't generally return to a decision once > made (and a GR would normally be the approach to overturning a TC > decision). Personally, I think there are circumstances where we might > (e.g. a convincing argument that we missed something critical in our > decision-making, or that circumstances have changed sufficiently to > warrant another look), but I don't think we are in that situation here > at the moment. > > I think the best way to proceed would be to open a bug describing the problem > that Simon outlines with RC severity; the relevant maintainers and release > team can then discuss how to resolve the issues and if they warrant delaying > the release or adjusting when we complete the transition. Obviously those > people might want to ask the TC for advice, but I think that would be up to > them at least in the first instance. Thanks for this helpful perspective. -- Sean Whitton
signature.asc
Description: PGP signature
