Release preparation.

Author: metasim

notes/2.1.0.markdown

@@ -0,0 +1,10 @@
+# Release 2.1.0
+
+## New Features
+
+* Support for sbt 1.0.2 (@blast-hardcheese)
+
+## Maintenance
+
+* General code and dependency cleanup (@blast-hardcheese, @xuwei-k)
+* Fixed scripted tests to work with sbt 1.0.2 (@metasim)

notes/release-process.markdown

@@ -1,7 +1,11 @@
 # Release Process Outline
 
 
-4. Run `git clean -fdx`. This makes sure there are no unexpected dependencies or artifacts that could affect the build.
+1. Run `git clean -fdx`. This makes sure there are no unexpected dependencies or artifacts that could affect the build.
+
+
+
+
 1. Create a branch to do the release work on. Something like `release-<X>.<Y>.<Z>` is good.
 2. Write release notes in Markdown with filename  `notes/<X>.<Y>.markdown`. Go through the commit logs and collect the major new features, bug fixes, deprecations, and anything else relevant to users. Making note of breaking changes is particularly important.
 5. Run `git tag -u <GPG key id> v<X>.<Y>.<Z> && git push`. This creates the tag that the `sbt-git` plugin will use to extract the artifact version number and publishes it. Providing a GPG key is just good form. [Here's some documention](http://www.dewinter.com/gnupg_howto/english/GPGMiniHowto-3.html) on how to get set up to have one.

version.sbt

@@ -1 +1 @@
-version in ThisBuild := "2.1.0-SNAPSHOT"
+version in ThisBuild := "2.1.0"