<commit_before>0.6.2
-----
* Fixing bug where `TenacityPropertyStore` wouldn't properly update the `executionIsolationStrategy` to reflect the live configuration value. This only affects Breakerbox's ability to determine
  if configurations are synchronized or not.

0.6.1
-----
* Remove `ManagedConcurrencyStrategy` and revert back to the default. This is replicated through `ManagedHystrix`. 
  Hystrix also enforces stricter use of `HystrixRequestContext` semantics when using a custom strategy. This broke use of per-request
  features of Hystrix.

0.6.0
-----
* Dropwizard 0.8.1 - This was blocked by [Dropwizard 0.8.0 pull-request](https://github.com/dropwizard/dropwizard/pull/939)


Dropwizard 0.7.x Releases
=========================

0.5.5
-----
* Backport of 0.6.1

0.5.4
--------------
* [Hystrix 1.4.4](https://github.com/Netflix/Hystrix/blob/master/CHANGELOG.md#version-144-maven-central-bintray)
* `executionIsolationStrategy` is now a configurable through `TenacityConfiguration`. Defaults to `THREAD` isolation. You'd want to normally
  set this to `SEMAPHORE` when using `TenacityObservableCommand`.
  [Breakerbox](https://github.com/yammer/breakerbox) will have a respective update which will also allow you set the `executionIsolationStrategy`.
* Fixing bug where the `TenacityPropertyRegister` would rely on the `toString()` method of the TenacityPropertyKey instead of `name()`.

0.5.3
--------------
* Added `SemaphoreConfiguration`. This enables the ability to configure semaphore specific parameters for when dealing with<commit_msg>Adding backport release of 0.5.6 for 0.6.2<commit_after>0.6.2
-----
* Fixing bug where `TenacityPropertyStore` wouldn't properly update the `executionIsolationStrategy` to reflect the live configuration value. This only affects Breakerbox's ability to determine
  if configurations are synchronized or not.

0.6.1
-----
* Remove `ManagedConcurrencyStrategy` and revert back to the default. This is replicated through `ManagedHystrix`. 
  Hystrix also enforces stricter use of `HystrixRequestContext` semantics when using a custom strategy. This broke use of per-request
  features of Hystrix.

0.6.0
-----
* Dropwizard 0.8.1 - This was blocked by [Dropwizard 0.8.0 pull-request](https://github.com/dropwizard/dropwizard/pull/939)


Dropwizard 0.7.x Releases
=========================

0.5.6
-----
* Backport of 0.6.2

0.5.5
-----
* Backport of 0.6.1

0.5.4
--------------
* [Hystrix 1.4.4](https://github.com/Netflix/Hystrix/blob/master/CHANGELOG.md#version-144-maven-central-bintray)
* `executionIsolationStrategy` is now a configurable through `TenacityConfiguration`. Defaults to `THREAD` isolation. You'd want to normally
  set this to `SEMAPHORE` when using `TenacityObservableCommand`.
  [Breakerbox](https://github.com/yammer/breakerbox) will have a respective update which will also allow you set the `executionIsolationStrategy`.
* Fixing bug where the `TenacityPropertyRegister` would rely on the `toString()` method of the TenacityPropertyKey instead of `name()`.

0.5.3
--------------
* Added `SemaphoreConfiguration`. This enables the ability to configure semaphore specific parameters for when dealing with
{'fraction_non_alphanumeric': 0.12964128382630585, 'fraction_numerical': 0.027690371302706105, 'mean_word_length': 4.135702746365105, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3648006', 'n_tokens_mistral': 979, 'n_tokens_neox': 918, 'n_words': 315}