From 555f7d07dc451c32317e9cb36d75c34a637fe02b Mon Sep 17 00:00:00 2001 From: Mathieu Leplatre Date: Fri, 27 Jan 2017 10:28:59 +0100 Subject: [PATCH] Preparing release 0.2.0 --- CHANGELOG.rst | 2 +- README.rst | 20 +++++++++----------- setup.py | 2 +- 3 files changed, 11 insertions(+), 13 deletions(-) diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 3016241..5cc5968 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -3,7 +3,7 @@ Changelog This document describes changes between each past release. -0.2.0 (unreleased) +0.2.0 (2017-01-27) ------------------ **New features** diff --git a/README.rst b/README.rst index 580579d..9c13973 100644 --- a/README.rst +++ b/README.rst @@ -68,21 +68,21 @@ The metadata on the collection must look like this: .. code-block:: js - { - "kinto-emailer": { - "hooks": [{ - "template": "Something happened!", - "recipients": ['Security reviewers '] - }] + { + "kinto-emailer": { + "hooks": [{ + "template": "Something happened!", + "recipients": ['Security reviewers '] + }] + } } - } In the above example, every action on the collection metadata or any record in that collection will trigger an email notification. Optional: -* ``sender`` (e.g.``"Kinto team "``) +* ``sender`` (e.g. ``"Kinto team "``) Recipients @@ -159,9 +159,7 @@ To run the unit tests:: $ make tests -For the functional tests, run a Kinto instance in a separate terminal: - -:: +For the functional tests, run a Kinto instance in a separate terminal:: $ make run-kinto diff --git a/setup.py b/setup.py index 8f2a5d1..6f74666 100644 --- a/setup.py +++ b/setup.py @@ -22,7 +22,7 @@ def read_file(filename): ] setup(name='kinto-emailer', - version='0.2.0.dev0', + version='0.2.0', description='Kinto emailer plugin', long_description=README + "\n\n" + CHANGELOG + "\n\n" + CONTRIBUTORS, license='Apache License (2.0)',