Release datadog-api-client-1.0.0-beta.2 (#282)

Author: nmuesch

CHANGELOG.md

@@ -1,5 +1,18 @@
 # CHANGELOG
 
+## datadog-api-client-1.0.0-beta.2 / 2020-05-04
+
+* [Added] Add some missing attributes to synthetics schemas. See [#265](https://github.com/DataDog/datadog-api-client-java/pull/265).
+* [Fixed] Monitor Query Descriptions. See [#278](https://github.com/DataDog/datadog-api-client-java/pull/278).
+* [Fixed] Synthetics Test Mark method and url as optional. See [#268](https://github.com/DataDog/datadog-api-client-java/pull/268).
+* [Fixed] Clean up generated client documentation. See [#260](https://github.com/DataDog/datadog-api-client-java/pull/260).
+* [Fixed] Add missing page query parameters. See [#253](https://github.com/DataDog/datadog-api-client-java/pull/253).
+* [Fixed] Update error responses for roles v2 endpoints. See [#252](https://github.com/DataDog/datadog-api-client-java/pull/252).
+* [Fixed] Bump jackson-databind from 2.9.10.3 to 2.9.10.4. See [#250](https://github.com/DataDog/datadog-api-client-java/pull/250).
+* [Fixed] Bump jackson-databind from 2.9.10 to 2.9.10.3. See [#246](https://github.com/DataDog/datadog-api-client-java/pull/246).
+* [Fixed] Add missing get ListSLO's 404 response. See [#247](https://github.com/DataDog/datadog-api-client-java/pull/247).
+* [Removed] Remove Pagerduty endpoint. See [#267](https://github.com/DataDog/datadog-api-client-java/pull/267).
+
 ## 1.0.0-beta.1 / 2020-04-22
 
 * [Added] Initial beta release of the Datadog API Client

RELEASING.md

@@ -11,22 +11,22 @@ This project does not have a strict release schedule. However, we would make a r
 ### Prerequisites
 - Install [datadog_checks_dev](https://datadog-checks-base.readthedocs.io/en/latest/datadog_checks_dev.cli.html#installation) using Python 3
 - Have [Java 1.8](https://www.oracle.com/java/technologies/javase-jdk8-downloads.html)
-- Ensure all CIs are passing on the master branch that we're about to release. 
-- Set the `BINTRAY_USER` and `BINTRAY_API_KEY` environment variables so that the release process can deploy to Bintray. 
+- Ensure all CIs are passing on the master branch that we're about to release.
+- Set the `BINTRAY_USER` and `BINTRAY_API_KEY` environment variables so that the release process can deploy to Bintray.
 
 ## Release
 Note that once the release process is started, nobody should be merging/pushing anything.
 
 ### 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
+- Run `ddev release changelog . <NEW_VERSION> --tag-prefix datadog-api-client-` 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 after you:
     - Make sure that all CIs are passing, as this is the commit we will be releasing!
 
 - Pull the latest changes after merging the above PR.
 - Run `mvn --settings settings.xml clean release:prepare` and follow the prompts to update the version and tag the repository.
-- Run `mvn --settings settings.xml release:perform` to deploy the artifact to Bintray. 
+- Run `mvn --settings settings.xml release:perform` to deploy the artifact to Bintray.
 - Find the artifact in Bintray and publish to make it visible to all.
 - Within Bintray, sync the specified version to maven central.
 
@@ -36,4 +36,4 @@ After merging the above PR, create a release on the [releases page](https://gith
 - Choose the tag that was created by the `mvn release:prepare` step
 - Place the changelog contents into the description of the release.
 - Attach the built Jar file into the release
-- Create/Publish the release, which will automatically create a tag on the `HEAD` commit. 
+- Create/Publish the release, which will automatically create a tag on the `HEAD` commit.