debian: Rework historical changelog

Rewriting history is generally considered a "not-so-good" thing, however here the historical data does not align with best practises and therefore it is beneficial to provide a better example going forward. There is only one initial release. Everything following that should list some kind of release notes or changelog, or at the very least just say something along the lines of "New version" rather than "Initial release". In this commit, the Git history is used for this task, filtering out "Makefile" changes as to retain only changes that are visible to users, excluding building tooling. For Debian packages, upon release, the target distribution should be updated to "unstable" (or "experimental" if preferred for any reason) when a release is finalized. During development, an invalid distribution name is expected to be there for tracking unreleased changes. That is why "UNRELEASED" is the standard way of specifying ongoing development, being an invalid distribution name itself. The "(Closes: #XXXXXX)" tag is intended for linking to Debian bug tracker, such as linking to the initial Intent to Package ticket, or later update/bugfix tickets. There does not appear to be a bug tracker in use for this task here, and the XXXXXX bug ticket number does not take you anywhere. It's therefore better to just remove it. Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

debian: Rework historical changelog
Rewriting history is generally considered a "not-so-good" thing, however here the historical data does not align with best practises and therefore it is beneficial to provide a better example going forward. There is only one initial release. Everything following that should list some kind of release notes or changelog, or at the very least just say something along the lines of "New version" rather than "Initial release". In this commit, the Git history is used for this task, filtering out "Makefile" changes as to retain only changes that are visible to users, excluding building tooling. For Debian packages, upon release, the target distribution should be updated to "unstable" (or "experimental" if preferred for any reason) when a release is finalized. During development, an invalid distribution name is expected to be there for tracking unreleased changes. That is why "UNRELEASED" is the standard way of specifying ongoing development, being an invalid distribution name itself. The "(Closes: #XXXXXX)" tag is intended for linking to Debian bug tracker, such as linking to the initial Intent to Package ticket, or later update/bugfix tickets. There does not appear to be a bug tracker in use for this task here, and the XXXXXX bug ticket number does not take you anywhere. It's therefore better to just remove it. Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
17c13870 · Valters Jansons · Michael Tremer · 12a8a35b · 17c13870
Commit 17c13870 authored Apr 12, 2021 by Valters Jansons Committed by Michael Tremer Apr 14, 2021
Show whitespace changes
Inline Side-by-side

Showing with 11 additions and 4 deletions

debian/changelog debian/changelog +11 -4

No files found.
--- a/debian/changelog
+++ b/debian/changelog
-libloc (0.9.6-1) UNRELEASED; urgency=medium
+libloc (0.9.6-1) unstable; urgency=medium

-  * Initial release. (Closes: #XXXXXX)
+  * location-importer.in: skip networks with unknown country codes
+  * location-importer.in: process unaligned IP ranges in RIR data files
+    correctly
+  * database: Free mmapped countries section
+  * location-importer.in: reduce log noise for unusable networks
+  * location-importer.in: delete 6to4 IPv6 space as well
+  * location-importer.in: fix typo
+  * location: Fix list-networks-by-as

 -- Michael Tremer <michael.tremer@ipfire.org>  Wed, 31 Mar 2021 14:06:00 +0100

-libloc (0.9.5-1) UNRELEASED; urgency=medium
+libloc (0.9.5-1) unstable; urgency=medium

-  * Initial release. (Closes: #XXXXXX)
+  * Initial release.

 -- Stefan Schantl <stefan.schantl@ipfire.org>  Sun, 27 Oct 2019 18:55:44 +0100