Release 0.10.1 as 1.0.0

Release 0.10.1

Release 0.10.0

 - A `NIL` hierarchy delimiter in a `Name` is now properly parsed and exposed as `None`
 - `RFC822.TEXT` responses are now returned by `Fetch::text()`.

Release 0.10.0

 - A `NIL` hierarchy delimiter in a `Name` is now properly parsed and exposed as `None`
 - `RFC822.TEXT` responses are now returned by `Fetch::text()`.

Release 0.9.5

This release adds support for stable Rust versions back to 1.26.2.

It also includes significantly improve integration testing by running
tests against a real IMAP server in CI (jonhoo#102, jonhoo#103).

Release 0.9.4 to expose new repository location

Release 0.9.3

Passing `None` to `list` should now no longer fail.

All string arguments can now be any type that implements `AsRef<str>`
(or `AsRef<[u8]>` for bytes). This should make the API much nicer to
use, and is backwards compatible.

Release 0.9.2 to update `README`

Quick-release of 0.9.1 to make clippy clean

Yanks 0.9.0 since API changed in uninteresting ways, and 0.9 is fresh.

Long overdue release of 0.9.0

This comes with a *long* list of changes:

The crate documentation, organization, and API has been significantly
improved:
https://github.com/mattnenterprise/rust-imap/compare/bddfab357fb6d83a472f8c538dc9fabe85108729..fc935bf88484808e37ad804c7badc9e0eb746d45

Several new IMAP features are supported:

 - `SEARCH` and `UID SEARCH`: jonhoo#89
 - `MOVE` and `UID MOVE`: jonhoo#88
 - `UID EXPUNGE`: jonhoo#87

We also now handle unilateral server responses (jonhoo#81 + jonhoo#91).

The client interface has been split into "unauthenticated" and
"authenticated" types to make the type system enforce user
authentication (jonhoo#84). In addition, custom authenticators (using the
`Authenticator` trait) no longer need to remember to base64
encode/decode challenges and responses themselves (jonhoo#97 + jonhoo#98).

In addition, lots of dependencies have also been bumped (`regex`,
`base64`, `nom`, `tokio-proto`, `native-tls`, etc.).

Lots of thanks to everyone who helped make all of this possible!
@greenpdx, @dario23, @VictorKoenders, @vandenoever, @mtorromeo,
@domcorvasce, @kmkaplan