From ff598e995d029a443d7e62c577240a9e684e66c3 Mon Sep 17 00:00:00 2001 From: Sebastian Wagner Date: Mon, 14 Oct 2019 14:48:35 +0200 Subject: [PATCH] REL: Maintenance release 2.0.2 --- CHANGELOG.md | 18 +++++++++--------- NEWS.md | 12 ++---------- debian/changelog | 6 ++++++ docs/Release.md | 10 +++++++--- intelmq/version.py | 2 +- 5 files changed, 25 insertions(+), 23 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ca299edc6..b5b7ed359 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,11 +2,9 @@ CHANGELOG ========== -2.0.2 (unreleased) +2.0.2 (2019-10-14) ----------------- -### Configuration - ### Core - `intelmq.lib.bot.CollectorBot`: Support the deprecated parameter `feed` until version 2.2 as the documentation was not properly updated (#1445). - `intelmq.lib.bot.Bot`: @@ -22,10 +20,6 @@ CHANGELOG - use default SSL context for client purposes, fixes compatibility with python < 3.6 if TLS is used. - Reconnect once on sending messages if disconnect detected. -### Development - -### Harmonization - ### Bots #### Collectors - `intelmq.bots.collectors.api.collector_api`: @@ -55,8 +49,6 @@ CHANGELOG #### Outputs - `intelmq.bots.outputs.amqptopic.output`: use default SSL context for client purposes, fixes compatibility with python < 3.6 if TLS is used. -### Documentation - ### Packaging - Rules: - Exclude intelmqsetup tool in packages @@ -84,6 +76,14 @@ CHANGELOG - Add `PIDFile` parameter to service file. ### Known issues +- MongoDB authentication: compatibility on different MongoDB and pymongo versions (#1439) +- ctl: shell colorizations are logged (#1436) +- http stream collector: retry on regular connection problems? (#1435) +- tests: capture logging with context manager (#1342) +- Bots started with IntelMQ-Manager stop when the webserver is restarted. (#952) +- n6 parser: mapping is modified within each run (#905) +- reverse DNS: Only first record is used (#877) +- Corrupt dump files when interrupted during writing (#870) 2.0.1 (2019-08-23) diff --git a/NEWS.md b/NEWS.md index b91875021..064a92d23 100644 --- a/NEWS.md +++ b/NEWS.md @@ -4,14 +4,10 @@ NEWS See the changelog for a full list of changes. -2.0.2 Bugfix release (unreleased) +2.0.2 Bugfix release (2019-10-14) --------------------------------- -### Requirements - -### Tools - -### Harmonization +Run `intelmqctl upgrade-config` and `intelmqctl check` after the upgrade. ### Configuration The deprecated parameter `feed` for collectors is again supported as the documentation as not properly updated. The support will be removed before version 2.2. @@ -26,10 +22,6 @@ The Cymru CAP Feed is (being) migrated to a new URL with a different format and #### Cymru Whois Expert, Modify Expert & Reverse DNS Expert These bots overwrite existing fields by default. A parameter `overwrite` has been added to make this optional, with the default value of `True` for backwards compatibility. If the parameter is not set, a warning is logged. The default value will change to `False` in version 3.0.0. The default for all new bots (in `BOTS`) is `False` already. -### Libraries - -### Postgres databases - 2.0.1 Bugfix release (2019-08-23) --------------------------------- diff --git a/debian/changelog b/debian/changelog index 1e1fa46c2..16ed6d837 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +intelmq (2.0.2-1) stable; urgency=medium + + * Update to 2.0.2. + + -- Wagner Sebastian Mon, 14 Oct 2019 14:47:52 +0200 + intelmq (2.0.1-2) stable; urgency=medium * Backport "intelmqctl: Fix `upgrade-conf` is state file is empty or not existing." diff --git a/docs/Release.md b/docs/Release.md index 539237026..776613ec1 100644 --- a/docs/Release.md +++ b/docs/Release.md @@ -9,10 +9,14 @@ - [Announcements](#announcements) - [Prepare new version](#prepare-new-version) -Make sure the current state is really final ;) -You can test most of the steps described here locally before doing it real. -Assumption: You are working on branch maintenance, the next version is a bug fix release. For feature releaese it is slightly different. +General assumption: You are working on branch maintenance, the next version is a bug fix release. For feature releaese it is slightly different. + +## Check before + + * Make sure the current state is really final ;) + You can test most of the steps described here locally before doing it real. + * Check the upgrade functions in `intelmq/lib/upgrades.py`. ## Documentation diff --git a/intelmq/version.py b/intelmq/version.py index 74c4f7eee..c07c0b075 100644 --- a/intelmq/version.py +++ b/intelmq/version.py @@ -1,2 +1,2 @@ -__version_info__ = (2, 0, 2, 'alpha', 1) +__version_info__ = (2, 0, 2) __version__ = '.'.join(map(str, __version_info__))