Hello Bill, On Wed, Jan 03 2018, Bill Allombert wrote: > Standards-Version is purely informational. All packages are expected > to comply with the latest policy, and respectively, when policy > changes are proposed, we are careful to check what packages are > impacted and what should be done about them. If the change is minor, > often a lintian warning is enough. Otherwise bugs are reported > > So it is not a big problem if one update Standards-Version without > actually checking policy, as long as one check the lintian warnings > and the BTS. You seem to be suggesting that the Policy Editors ensure that for every change of Policy there is either a new Lintian tag or an MBF? If that's what you mean, then it's completely false, and if we did require ourselves to do that, there would never be any releases of Policy :) (it is, though, true that we check what packages are impacted and what should be done about them) > On the other hand it should not be done in NMU, because some > maintainers use this field to track of far they checked the > upgrading-checklist file for this package. I don't understand what role there could be for the upgrading checklist if every change has an accompanying Lintian tag or MBF. Perhaps you could rephrase this remark about NMUs. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature