REL: Release version 1.1.2

CHANGELOG.md

@@ -1,15 +1,13 @@
 CHANGELOG
 ==========
 
-1.1.2 (unreleased)
+1.1.2 (2019-03-25)
 ------------------
 
 ### Core
 - `intelmq.lib.bot`:
   - `Bot.__handle_sighup`: Handle exceptions in `shutdown` method of bots.
 
-### Development
-
 ### Harmonization
 - FQDN: Disallow `:` in FQDN values to prevent values like '10.0.0.1:8080' (#1235).
 
@@ -63,9 +61,9 @@ CHANGELOG
   - status: Show commandline differences if a program with the expected PID could be found, but they do not match (previous output was `None`).
   - Use logging level from defauls configuration if possible, otherwise intelmq's internal default. Previously, DEBUG was used unconditionally.
 
-### Contrib
-
 ### Known issues
+- Bots started with IntelMQ-Manager stop when the webserver is restarted (#952).
+- stomp collector bot constantly uses 100% of CPU (#1364).
 
 
 1.1.1 (2019-01-15)

NEWS.md

@@ -3,31 +3,20 @@ NEWS
 
 See the changelog for a full list of changes.
 
-1.1.2 Bugfix release (unreleased)
+1.1.2 Bugfix release (2019-03-25)
 ---------------------------------
 
 ### Configuration
 #### Feodotracker
  * The URL of the "Feodo Tracker IPs" feed has changed. The new one is `https://feodotracker.abuse.ch/downloads/ipblocklist.csv`. If you are using this feed, adapt your configuration accordingly. The parser has been updated to support the new format.
- * The feed ""Feodo Tracker Domains" has been discontinued.
-
-### Libraries
-
-### Postgres databases
-
+ * The feed "Feodo Tracker Domains" has been discontinued.
 
 1.1.1 Bugfix release (2019-01-15)
 ---------------------------------
 
-### Tools
-
-### Harmonization
-
 ### Configuration
 In 1.1.0 the default value for the parameter `error_dump_message` was set to `false`. The recommended value, used in previous and future release is `true` to not loose any data in case of errors. Users are advised to check the values configured in their `defaults.conf` file.
 
-### Libraries
-
 ### Postgres databases
 The following statements optionally update existing data.
 Please check if you did use these feed names and eventually adapt them for your setup!
@@ -252,8 +241,6 @@ UPDATE events
 1.0.6 Bugfix release (2018-08-31)
 ---------------------------------
 
-### Configuration
-
 ### Libraries
 - Some optional dependencies do not support Python 3.3 anymore. If your are still using this unsuported version consider upgrading. IntelMQ 1.0.x itself is compatible with Python 3.3.
 

debian/changelog

@@ -1,8 +1,8 @@
-intelmq (1.1.2~alpha1-1) unstable; urgency=medium
+intelmq (1.1.2) stable; urgency=medium
 
   * Update to version 1.1.2.
 
- -- Wagner Sebastian <[email protected]>  Tue, 15 Jan 2019 17:03:15 +0100
+ -- Wagner Sebastian <[email protected]>  Mon, 25 Mar 2019 15:29:02 +0100
 
 intelmq (1.1.1-1) stable; urgency=medium
 

docs/Release.md

@@ -30,7 +30,7 @@ Why a separate branch? Because if problems show up, you can still force-push to
 
 ## Tag and release
 
-Tag the commit with `git tag -s version HEAD`, merge it into master, push the both branches *and* the tag. The tag is just `a.b.c`, not prefixed with `v` (that was necessary only with SVN a long time ago...).
+Tag the commit with `git tag -s version HEAD`, merge it into master, push the branches *and* the tag. The tag is just `a.b.c`, not prefixed with `v` (that was necessary only with SVN a long time ago...).
 
 Go to https://github.com/certtools/intelmq/tags and enter the release notes (changelog) for the new tag, then it's considered a release by github.
 
@@ -92,6 +92,12 @@ Add a new empty changelog and news section. For the changelog:
 And for the news:
 
 ```
+### Requirements
+
+### Tools
+
+### Harmonization
+
 ### Configuration
 
 ### Libraries

intelmq/version.py

@@ -1,2 +1,2 @@
-__version_info__ = ('1', '1', '2', 'alpha1')
+__version_info__ = ('1', '1', '2')
 __version__ = '.'.join(__version_info__)