[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Why bother with ITP bugs?



On Mon, Jan 17, 2022 at 10:23:51PM -0800, Ross Vandegrift wrote:
> I guess ITP bugs are common practice for new packages... but are they
> *required* by anything?
No. But your sponsor is likely to request you to file one before
sponsoring.

> It seems like fairly high-friction, low-value work - especially if
> you're talking about more than a single package.  So I'd like to avoid
> it, but I'm not sure what the costs would be.
Main benefits of an ITP:
- It is supposed to act like a mutex, signalling that someone is already
  packaging this. But this often doesn't work as intended because people
  learn about ITPs only when they first run lintian, not before starting
  the work, so there are multiple cases of several people working on the
  same package separately.
- After it's announced on d-devel@, people can look at it and send their
  thoughts (up to, as happens from time to time, telling the packager that
  the software is already in Debian).
- The packager may decide to send the progress/status reports to the bug,
  which can help other people.

-- 
WBR, wRAR

Attachment: signature.asc
Description: PGP signature


Reply to: