Simplify release procedure (#97)

Author: raboof

RELEASING.md

@@ -1,10 +1,5 @@
 # Releasing
 
-1. Check [closed issues without a milestone](https://github.com/lightbend/sbt-paradox-apidoc/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20no%3Amilestone) and either assign them the upcoming release milestone or 'invalid'
-1. Create a [new release](https://github.com/lightbend/sbt-paradox-apidoc/releases/new) with:
-    * the next tag version (e.g. `v0.2`)
-    * title and release description including notable changes
-    * link to the [milestone](https://github.com/lightbend/sbt-paradox-apidoc/milestones) showing an overview of closed issues for this release
-    * overview of contributors generated by [`sbt-authors`](https://github.com/2m/authors) (eg. `sbt authors v0.1 v0.2`)
+1. Wait until all running [Travis CI jobs](https://travis-ci.org/lightbend/sbt-paradox-apidoc/builds) complete, if any.
+1. Fix up the [draft release](https://github.com/lightbend/sbt-paradox-apidoc/releases) created by the release drafter and set the next tag version (e.g. `v0.2`)
 1. Travis CI will start a [CI build](https://travis-ci.org/lightbend/sbt-paradox-apidoc/builds) for the new tag and publish artifacts to Bintray.
-1. Close the milestone for this release and start a new one.