Dear Russ, [Disclaimer: the words below are as a member of the release team, but not necessarily those of the team. We haven't discussed this yet.] On 17-11-2019 20:47, Russ Allbery wrote: > Let me copy the release team. How would you all prefer to handle the > relationship between release-criticality and Policy requirements? I don't > think as a project it's ideal to maintain two separate lists of > requirements, but Policy currently doesn't have a nice summary list like > that. > > One possible option would be for Policy to take over maintenance of a > summary list of all Policy requirements, and then the release team can > maintain only a list of exceptions for a given Debian release. Do you > think that might be an improvement? I think this would be an improvement, yes. As you can see at the top of our policy, the list hasn't seen real proper review for years, although some months ago I went through our policy to add cross-references to Policy where I could find them. Those without the links would probably be the RT amendments. I would love to have a list with the other items to *also* be able to spot which ones aren't on our list (but should). I can envision that if Policy carries such a summary list, our policy would mention the version of Policy it was based on, to make sure that Policy doesn't suddenly change what we as the RT agreed on. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature