0.1.1

-----

linkerd-tcp 0.1.1 focuses on improving TLS support, and on updating linkerd-tcp's
dependencies.

* Trace negotiated SNI & ALPN at the end of the server handshake.
* Improve handling and reporting of TLS configuration errors.
* Update to latest versions of dependencies.
* Switch the official Rust base docker image.
* Remove use of deprecated downstream API members.
* Remove dependency on nightly Rust to build linkerd-tcp.

Rewrite linkerd-tcp (#63)

linkerd-tcp 0.1.0 constitutes a major rewrite.

Previously, linkerd-tcp did not properly utilize tokio's task model, which lead
to a number of performance and correctness problems. Furthermore, linkerd-tcp's
configuration interface was substantially different from linkerd's, which
caused some confusion.

Now, linkerd-tcp has been redesigned:
- to better-leverage tokio's reactor;
- to support connection and stream timeouts;
- to provide much richer metrics insight;
- to be structured like a linkerd-style router;
- general correctness improvements.

Fixes #26 #40 #49 #50
Depends on linkerd/tacho#20

Update CHANGES.md for 0.0.3 release (#33)

* Update CHANGES.md for 0.0.3 release

* Reword connection leak fix

Add a CHANGES.md file, prep for 0.0.2 release (#12)

Make the namerd stream resilient to failures (#7)

Recently the semantics of `futures::Stream` changed such that errors are
terminal.

Now, we ensure that individual namerd request failures are not propagated onto
the address stream.

Furthermore, configuration files have been made more brittle so that unknown
fields are not silently ignored.