Release 0.34.0 (#524)

CHANGELOG.md

@@ -1,5 +1,20 @@
 CHANGELOG
 =========
+## 0.34.0 / 2020-02-04
+
+* [Deprecated] Alias `dog` script names as `dogshell`. Please start using `dogshell` instead of `dog` command. See [#305](https://github.com/DataDog/datadogpy/pull/305). Thanks [dwminer](https://github.com/dwminer).
+* [Fixed] [dogshell] Enforce the default 'normal' event priority client side. See [#511](https://github.com/DataDog/datadogpy/pull/511).
+* [Fixed] [dogstatsd] Handle EAGAIN socket error when dropping packets. See [#515](https://github.com/DataDog/datadogpy/pull/515). Thanks [mrknmc](https://github.com/mrknmc).
+* [Fixed] [dogstatsd] Handle OSError on socket.close on Python 3.6+. See [#510](https://github.com/DataDog/datadogpy/pull/510). Thanks [charettes](https://github.com/charettes).
+* [Added] [dogstatsd] Add `statsd_constant_tags` kwarg to datadog.initialize(). See [#494](https://github.com/DataDog/datadogpy/pull/494). Thanks [kainswor](https://github.com/kainswor).
+* [Added] [dogstatsd] Adding telemetry to dogstatsd. See [#505](https://github.com/DataDog/datadogpy/pull/505).
+* [Added] [dogwrap] Add duration as metric. See [#506](https://github.com/DataDog/datadogpy/pull/506).
+* [Added] [dogwrap] Add option to send to EU endpoint. See [#502](https://github.com/DataDog/datadogpy/pull/502).
+* [Added] [dogwrap] Add warning option for dogwrap based on exit codes. See [#471](https://github.com/DataDog/datadogpy/pull/471). Thanks [dabcoder](https://github.com/dabcoder).
+* [Added] Include LICENSE in MANIFEST.in. See [#500](https://github.com/DataDog/datadogpy/pull/500). Thanks [jjhelmus](https://github.com/jjhelmus).
+* [Added] Add base class for all exceptions. See [#496](https://github.com/DataDog/datadogpy/pull/496). Thanks [hakamadare](https://github.com/hakamadare).
+* [Added] Tag normalization. See [#489](https://github.com/DataDog/datadogpy/pull/489).
+
 
 # 0.33.0 / 2019-12-12
 

RELEASING.md

@@ -1,5 +1,4 @@
 # Releasing
-
 This document summarizes the process of doing a new release of this project.
 Release can only be performed by Datadog maintainers of this repository.
 
@@ -9,7 +8,6 @@ This project does not have a strict release schedule. However, we would make a r
   - Releases may be done more frequently than the above mentioned window.
 
 ## Make Sure Everything Works
-
 * Check and upgrade dependencies where it applies and makes sense. [Example](https://github.com/DataDog/datadogpy/commit/f81efe8cbf6e5bc5cb4ab46da750248161d0c548#diff-2eeaed663bd0d25b7e608891384b7298)
   - Create a distinct pull request and test your changes since it may introduce regressions.
   - While using the latest versions of dependencies is advised, it may not always be possible due to potential compatibility issues.
@@ -19,32 +17,24 @@ This project does not have a strict release schedule. However, we would make a r
 * Make sure documentation is up-to-date and building correctly.
 * Build the package locally (e.g. `python3 setup.py sdist`), install it into a fresh virtualenv and test the changes that have been made since the last release.
 
-## Update Changelog
-
-### Prerequisite
-
-- Install [datadog_checks_dev](https://datadog-checks-base.readthedocs.io/en/latest/datadog_checks_dev.cli.html#installation) using Python 3
-
-### Commands
-
-- See changes ready for release by running `ddev release show changes .` at the root of this project. Add any missing labels to PRs if needed.
-- Run `ddev release changelog . <NEW_VERSION>` to update the `CHANGELOG.md` file at the root of this repository
-- Commit the changes to the repository in a release branch and get it approved/merged.
-
 ## Release Process
-
 Our team will trigger the release pipeline.
 
-### Prerequisite
-
-#### Setup PyPI
+### Prerequisite 
+- Install [datadog_checks_dev](https://datadog-checks-base.readthedocs.io/en/latest/datadog_checks_dev.cli.html#installation) using Python 3.
+- Setup PyPI, see the internal documentation for more details
 
-In order to create a new release you will need to setup PyPI Tooling as well as `datadog_checks_dev` mentioned above.
-See our internal documentation for more details.
+### Update Changelog
+#### Commands
+- See changes ready for release by running `ddev release show changes .` at the root of this project. Add any missing labels to PRs if needed.
+- Run `ddev release changelog . <NEW_VERSION>` to update the `CHANGELOG.md` file at the root of this repository
+- Commit the changes to the repository in a release branch and open a PR. Do not merge yet.
 
 ### Release
-
+1. Bump the version in [`setup.py`](setup.py) and push it to your changelog PR. [Example](https://github.com/DataDog/datadogpy/pull/495/files#diff-2eeaed663bd0d25b7e608891384b7298)
+1. Merge the PR to master.
 1. Create the release on GitHub. [Example](https://github.com/DataDog/datadogpy/releases/tag/v0.33.0)
-2. Checkout the tag created at the previous step.
-3. Run `ddev release build .` and `ddev release upload --sdist . `.
+1. Checkout the tag created at the previous step.
+1. Run `ddev release build .` and `ddev release upload --sdist . `.
   - Make sure that both an `sdist` and a [universal wheel](https://packaging.python.org/guides/distributing-packages-using-setuptools/#universal-wheels) have been uploaded to [PyPI](https://pypi.python.org/pypi/datadog/).
+1. Bump the version again in `setup.py` to a dev version (e.g. `0.34.0` -> `0.35.0+dev`), open a PR and merge it to master.

setup.py

@@ -22,7 +22,7 @@ def get_readme_md_contents():
 
 setup(
     name="datadog",
-    version="0.33.0",
+    version="0.34.0",
     install_requires=install_reqs,
     tests_require=["pytest", "mock", "freezegun"],
     packages=["datadog", "datadog.api", "datadog.dogstatsd", "datadog.threadstats", "datadog.util", "datadog.dogshell"],