control: tag -1 +moreinfo Hello,
On Tue 01 Oct 2019 at 04:21PM +02, Mattia Rizzolo wrote: > On Tue, Oct 01, 2019 at 07:14:08AM -0700, Sean Whitton wrote: >> Hmm, this was deliberate because the additional documentation doesn't >> require anyone to make changes to their packages. >> >> Could you explain why you want it in the upgrading checklist? > > because it's a new thing, and it helps those people that don't follow > closely enough to know that there is a new thing. So if at some point > any given package start to need some "reboot required" information, > everybody who read once the checklist know that there already is a > policy/standard for that. Well, it's new to the Policy Manual, but it's certainly not new in the archive. > Like you document in the checklist addition to the virtual packages: > also those don't require any change to existing packages, it's just > there for everybody to know that starting from that version they can > make use of that new thing. Okay. From your point of view, if we started to add a summary of d/changelog entries which are /not/ accounted for by the upgrading checklist to the d-d-a e-mail, would that be sufficient? Or do you think this stuff has to be in the upgrading checklist? -- Sean Whitton
signature.asc
Description: PGP signature
