Prepare 2.0.1 release. (#188)

Remove remaining references to prerelease status.

Author: scouten

CHANGELOG.md

@@ -3,6 +3,21 @@
 This is a major rewrite of the previously-existing [`sqlite_ecto`](https://github.com/jazzyb/sqlite_ecto) that adds support for Ecto 2.1+.
 
 
+## v2.0.1
+
+_7 August 2017_
+
+* Formally announce availability.
+* Fix a few README and CHANGELOG issues.
+
+
+## v2.0.0
+
+_6 August 2017_
+
+* Fix a few documentation errors.
+
+
 ## v2.0.0-dev.8
 
 _11 June 2017_

README.md

@@ -14,11 +14,9 @@ Read [the tutorial](./docs/tutorial.md) for a detailed example of how to setup a
 
 *(and when not to use it ...)*
 
-**IMPORTANT!!!!** This is a preliminary, bleeding-edge release. It is believed to work with all 2.0.x and 2.1.x versions of Ecto, but it has not been subjected to any serious performance analysis or stress test. I recommend against deploying this into any sort of production environment at this time.
+If, for some reason, you still need to use Ecto 1.x, please look at [sqlite_ecto](https://github.com/jazzyb/sqlite_ecto), on which this project is based.
 
-If you're able to use Ecto 1.x, please look at [sqlite_ecto](https://github.com/jazzyb/sqlite_ecto), on which this project is based.
-
-Setting aside the prerelease nature of this library, I strongly recommend reading [Appropriate Uses for SQLite](https://sqlite.org/whentouse.html) on the SQLite page itself. All of the considerations mentioned there apply to this library as well.
+I strongly recommend reading [Appropriate Uses for SQLite](https://sqlite.org/whentouse.html) on the SQLite site itself. All of the considerations mentioned there apply to this library as well.
 
 I will add one more: If there is *any* potential that more than one server node will need to write directly to the database at once (as often happens when using Elixir in a clustered environment), **do not use** `sqlite_ecto2`. Remember that there is no separate database process in this configuration, so each of your cluster nodes would be writing to its **own** copy of the database without any synchronization. You probably don't want that. Look for a true client/server database (Postgres, MySQL, or similar) in that case. SQLite's sweet spot is single-machine deployments (embedded, desktop, etc.).
 

mix.exs

@@ -3,7 +3,7 @@ defmodule Sqlite.Ecto2.Mixfile do
 
   def project do
     [app: :sqlite_ecto2,
-     version: "2.0.0",
+     version: "2.0.1",
      name: "Sqlite.Ecto2",
      elixir: "~> 1.3.4 or ~> 1.4",
      elixirc_options: [warnings_as_errors: true],