docs(crate): Pre-release updating

- Update both readme's
- Update changelog
- Bump version to 0.6.0

Author: PTaylor-us

CHANGELOG.md

@@ -2,15 +2,20 @@
 
 ## [Unreleased]
 
+
+[unreleased]: https://github.com/FluenTech/embedded-time/compare/v0.6.0...HEAD
+
+## [0.6.0] - 2020-07-03
+
 ### Added
 
 - A `Timer` type supporting one-shot and periodic software timers utilizing a `Clock` implementation
-- `Timer` unit tests
-- Fallibility to `Clock` methods
+- Fallibility and error handling for `Clock` methods
 - `Instant::duration_until()` with order checking
 - Order checking to `Instant::duration_since()`
 - Bounds checking on `Instant` impls of Add/Sub
 - Changelog back to v0.5.0 release
+- [`crossbeam-utils`](https://crates.io/crates/crossbeam-utils) dev-dependency for scoped threads in tests
 
 ### Changed
 
@@ -19,7 +24,7 @@
 - `Instant::duration_since()` return type to `Result`
 - Refactor `examples/nrf52_dk`
 
-[unreleased]: https://github.com/FluenTech/embedded-time/compare/v0.5.2...HEAD
+[0.6.0]: https://github.com/FluenTech/embedded-time/compare/v0.5.2...v0.6.0
 
 ## [0.5.2] - 2020-06-21
 

README.md

@@ -5,12 +5,42 @@
 [docs.rs]: https://docs.rs/embedded-time/badge.svg
 
 `embedded-time` provides a comprehensive library for implementing abstractions over
-hardware and work with _clocks_, _instants_, _durations_, _periods_, and _frequencies_ in a more intuitive way.
- 
+hardware and work with _clocks_, _timers_, _instants_, _durations_, _periods_, and _frequencies_ in a more intuitive way.
+
+## Hardware Abstraction
+
 - `Clock` trait allowing abstraction of hardware timers for timekeeping.
-- Work with time using _milliseconds_, _seconds_, _hertz_, etc. rather than _cycles_ or _ticks_.
-- Includes example for the nRF52_DK board
-- Conversion to/from core::time::Duration
+
+## Timers
+
+- Software timers spawned from a `Clock` impl object.
+- One-shot or periodic/continuous
+- Blocking delay
+- Poll for expiration
+- Read elapsed/remaining duration
+
+## Duration Types
+
+- Nanoseconds
+- Microseconds
+- Milliseconds
+- Seconds
+- Minutes
+- Hours
+
+## Frequency Type
+
+- Hertz
+
+## `core` Compatibility
+
+- Conversion to/from `core::time::Duration`
+
+## Reliability and Usability
+- Extensive tests
+- Thorough documentation with examples
+- Example for the nRF52_DK board
+
 
 ## License
 This project is licensed under either of

crates-io.md

@@ -1,12 +1,41 @@
 # embedded-time
 
 `embedded-time` provides a comprehensive library for implementing abstractions over
-hardware and work with _clocks_, _instants_, _durations_, _periods_, and _frequencies_ in a more intuitive way.
- 
+hardware and work with _clocks_, _timers_, _instants_, _durations_, _periods_, and _frequencies_ in a more intuitive way.
+
+## Hardware Abstraction
+
 - `Clock` trait allowing abstraction of hardware timers for timekeeping.
-- Work with time using _milliseconds_, _seconds_, _hertz_, etc. rather than _cycles_ or _ticks_.
-- Includes example for the nRF52_DK board
-- Conversion to/from core::time::Duration
+
+## Timers
+
+- Software timers spawned from a `Clock` impl object.
+- One-shot or periodic/continuous
+- Blocking delay
+- Poll for expiration
+- Read elapsed/remaining duration
+
+## Duration Types
+
+- Nanoseconds
+- Microseconds
+- Milliseconds
+- Seconds
+- Minutes
+- Hours
+
+## Frequency Type
+
+- Hertz
+
+## `core` Compatibility
+
+- Conversion to/from `core::time::Duration`
+
+## Reliability and Usability
+- Extensive tests
+- Thorough documentation with examples
+- Example for the nRF52_DK board
 
 ## Motivation
 The handling of time on embedded systems is generally much different than that of OSs. For instance, on an OS, the time is measured against an arbitrary epoch. Embedded systems generally don't know (nor do they care) what the *real* time is, but rather how much time has passed since the system has started.