Policy 5.6.30 lists the Testsuite field, but it doesn't list the
Testsuite-Triggers field that seems to be part of Sources files and is
generated by dpkg-source >= 1.18.8.

This field is quite useful, as given my package src:foo, I can find out
which packages have autopkgtests that depend on it, and are thus in the
set of reverse dependencies that I could check for breakage.

I'd provide a patch based on the documentation in dsc(5), but I don't
know what the current process is. Does anyone have a link to a doc on
how to submit a change?

Best,
Christian

Hello,

There is a chapter of Policy regarding the Policy Changes Process.

Hi Sean,

ironically enough, I did find that one before I submitted, but I didn't
see this as a Policy change, instead as documenting a change that had
already happened. Which, in hindsight, was of course an erroneous
assumption.

I'll continue on the proper process after the three-day-weekend here in
Austria.

Best,
Christian

Hi again,

I've read up on the change process [1], and I guess my proposal to
submit a patch was too far into the process.

Thus, I take a step back, and seek discussion first.

In addition to what I've said above, I think documenting this field
would not only enhance discoverability, but give more weight to it for
tooling that makes use of these fields.

For discussion context, I'd like to quote dsc(5) on this field:
Best,
Christian

[1] https://www.debian.org/doc/debian-policy/ap-process.html

Hello,

Sounds good to me.  If you'd like to propose wording, there's some more
guidance in our README.md.  Thanks!