On Thu, 2022-04-28 at 20:24 +0200, Andreas Tille wrote: > But filing an ITP bug is cheap. The R-pkg team has a script > itp_from_debian_dir[1] which creates this bug automatically once the > packaging work is done.
The packaging work is supposed to start *after* the ITP is filed, so this is a suboptimal order to do things in and doesn't provide much value, except as a way to prevent people packaging the same R library during the wait in NEW, but the presence of the R library in the R-pkg team VCS already provides that, so the ITP bug isn't really needed. Even when filing ITPs before packaging, for language ecosystem teams where all library packages for the language go through the same team, team co-ordination mechanisms are probably enough of a way to prevent duplication of work, and that work is mostly automated anyway for several such teams, so the ITP bug mostly isn't really needed. Some teams make exceptions for packages that aren't strictly just libraries; for eg Rust folks to ITPs for things that ship executables, so that people can hear about things they might want to use on Debian. > That's true. I just wanted to mention that some of your ideas > are in a way used even now. Yeah, the proposal was derived from the suggestion to file ITPs for all NEW packages, mostly aimed at avoiding the deficiencies with that idea. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
