Cleanup changelog

Author: stanlemon

CHANGELOG.md

@@ -1,7 +1,7 @@
 # Change Log
 The format is based on [Keep a Changelog](http://keepachangelog.com/) and adheres to [Semantic Versioning](http://semver.org/).
 
-## 0.10.0 (RELEASE DATE TBD)
+## 0.10.0 (UNRELEASED)
 
 ### DynamicSpout Framework
 #### Breaking Changes
@@ -12,21 +12,20 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and adhere
 ### Improvements
 - [PR-38](https://github.com/salesforce/storm-dynamic-spout/pull/38) Removed unused method `Deserializer.getOutputFields()`.
 - [PR-37](https://github.com/salesforce/storm-dynamic-spout/pull/37) Added hasStep() and getStep() to `FilterChain` and added a specific exception for serializing/deserializing `FilterChainStep` objects. 
+- [PR-40](https://github.com/salesforce/storm-dynamic-spout/pull/40) Timer metrics will now publish a counter metric containing the total time spent within each metric key. Start publishing developer performance metrics within VirtualSpout via MetricRecorder.
+- [PR-45](https://github.com/salesforce/storm-dynamic-spout/pull/45) MetricRecorder is now passed into Consumer interface via open() method.
+- [PR-55](https://github.com/salesforce/storm-dynamic-spout/pull/55) Refactored how DynamicSpout coordinates with VirtualSpouts internally.
 - [PR-85](https://github.com/salesforce/storm-dynamic-spout/pull/85) Fix ordering bug in DefaultRetryManager. Always retry the earliest messageId.
 - [PR-90](https://github.com/salesforce/storm-dynamic-spout/pull/90) Adds new 'Permanently Failed' output stream. Tuples that exceed the configured retry limit will now be emitted out a 'failed' stream un-anchored. This allows you to do your own error handling within the topology by subscribing to this stream. The name of this output stream defaults to 'failed', but is configurable via the `spout.permanently_failed_output_stream_id` configuration item.
+- [PR-101](https://github.com/salesforce/storm-dynamic-spout/pull/101) Fix NPE in RatioMessageBuffer on Spout deploy.
+- [PR-104](https://github.com/salesforce/storm-dynamic-spout/pull/104) Allow curator exceptions to bubble up
 - [PR-110](https://github.com/salesforce/storm-dynamic-spout/pull/110) Fix exponential retry delay growth in DefaultRetryManager.
-- [ISSUE-100](https://github.com/salesforce/storm-dynamic-spout/issues/100) Fix NPE in RatioMessageBuffer on Spout deploy.
+- [PR-111](https://github.com/salesforce/storm-dynamic-spout/pull/111) Update dependencies and cleanup
 
 #### Removed
 - [PR-45](https://github.com/salesforce/storm-dynamic-spout/pull/45) Removed getMaxLag() from Consumer interface.
 - [PR-81](https://github.com/salesforce/storm-dynamic-spout/pull/81) Removed getPersistenceAdapter() from Consumer interface.
 
-#### Improvements
-- [PR-37](https://github.com/salesforce/storm-dynamic-spout/pull/37) Added hasStep() and getStep() to `FilterChain` and added a specific exception for serializing/deserializing FilterChainSteps.
-- [PR-40](https://github.com/salesforce/storm-dynamic-spout/pull/40) Timer metrics will now publish a counter metric containing the total time spent within each metric key. Start publishing developer performance metrics within VirtualSpout via MetricRecorder.
-- [PR-45](https://github.com/salesforce/storm-dynamic-spout/pull/45) MetricRecorder is now passed into Consumer interface via open() method.
-- [PR-55](https://github.com/salesforce/storm-dynamic-spout/pull/55) Refactored how DynamicSpout coordinates with VirtualSpouts internally.
-
 ### Sideline Framework
 In this release the 'stop' sideline state was split into 'resume' and 'resolve', allowing for one to begin processing a sideline without designating an ending offset and then applying an ending offset later on. Based upon our experience this is a more practical division of state for sidelining.