Guillem Jover writes ("Re: Bug#720507: .dsc field for dgit"):
> It seems premature to me to document this in policy while as you
> recognize elsewhere this is for now still just an experiment. In a way
> I guess I also fail to see the need to document it at all in policy
> given that it's a tool specific field (we have other such tool
> specific fields specified in external documents or policies). QA
> tools should be able to follow whatever spec the tool has designated
> for itself, no?For the reasons Joey explains, I would like it documented. Also, TBH, I don't think it is really right to have a lot of tool-specific fields which aren't documented in our reference manual. In principle this isn't a tool-specific field, in the sense that the specification is published and other machinery which wants to make use of it can do so. As for dgit still being an experiment: well, I think it's beyond that now. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21022.40371.723099.932...@chiark.greenend.org.uk
