Hello, On Mon 04 Nov 2019 at 04:42PM -05, Nicholas D Steeves wrote: > The current version is x.y.z.t (up to you to discover!), but the trailing > ".t" is dropped in the declared "Standards-Version" in control. Sean, > I've always wondered why this was the case and supposed that this is > because the ".t" is not significant enough to merit a new > Standards-Version, or possibly because the Standards-Version schema is > major.minor.patch_version (semantic versioning), where the ".t" is only > used for thing like typo fixes in Policy. Please comment :-) See Policy 5.6.11. If the final number changes, there is no change to the meaning of the standards, so there couldn't be any upgrading to packages to perform. > Sean, would you please say something about why meaningful > changelog entries are important, and why "* Bump standards-version" > isn't meaningful? It's one of the primary ways in which people working on Debian communicate. When something breaks, people need to be able to know whether your package might have had something to do with it without having to clone your whole git repository. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature