Release Hermes v0.6.0 (#1134)

* Bump crates to 0.6.0

* Update version number in guide

* Add documentation on config reload to the guide

* Add help section about state dump via `SIGUSR1` signal

* Add TOC to config guide page

* Update state dump guide section and link it from reload config section

* Added warning in guide config

* Fixed panic for clear_packets_interval

* Upgrade path in the changelog

* Guide upt for query channel ends

* config validate in the guide

* Update guide with new state dump format

* Update guide/src/config.md

Co-authored-by: Romain Ruetschi <[email protected]>

* Bump `ibc-proto` to v0.8.2

Co-authored-by: Adi Seredinschi <[email protected]>

Author: romac

CHANGELOG.md

@@ -1,28 +1,57 @@
 # Changelog
 
-## Unreleased
+## v0.6.0
+*July 12th, 2021*
 
 Many thanks to Fraccaroli Gianmarco (@Fraccaman) for helping us improve the
 reliability of Hermes ([#697]).
 
-__! Configuration file changes:__
-The Hermes config.toml configuration file has went through a few revisions
-in this release. The changes are as follows:
-- Added inline documentation for all options.
-- Added a filtering mechanism to allow packet relaying only on
-  specific channels. Consequently, there are two new options in the
-  configuration file:
-    1. A global `filter` parameter to enable or disable filtering globally.
-    2. A per-chain `.filters` option that expects a list of channel and
-       port identifiers, so that packet relaying will be restricted to this
-       list for the corresponding chain.
-- Added a packet clearing configuration option, to parametrize the frequency
-  at which Hermes will clear pending packets. This is a global option, called
-  `clear_packets_interval`, which applies to all chains in the configuration.
-
-Note that both the `filter` and `clear_packets_interval` features apply
-only to Hermes passive relaying mode (command `hermes start`), and will
-not affect the other commands.
+This release includes two major features to Hermes: (1) support for reloading
+the chains from the configuration file at runtime, and (2) a filtering mechanism
+to restrict Hermes activity based on predefined parameters (e.g., packet relaying
+on certain ports and channels exclusively, and ignoring activity for clients
+that have non-standard trust threshold).
+
+In addition to these two, we have also added a health checkup mechanism, plus new
+`config validate` and `query channel ends` CLIs.
+
+### Upgrading from 0.5.0 to 0.6.0
+
+When upgrading from Hermes v0.5.0 to v0.6.0, the most important
+point to watch out for is the configuration file.
+The Hermes config.toml configuration file has went through a few revisions,
+with the changes described below.
+
+#### Added inline documentation for all options.
+
+Please have a look around the [config.toml](./config.toml) directly.
+
+#### Added a packet filtering mechanism based on channel/port identifiers
+
+This feature will restrict the channels on which Hermes relays packets.
+There are two new options in the configuration file:
+
+1. A global `filter` parameter to enable or disable filtering globally.
+2. A per-chain `.filters` option that expects a `policy` (either `allow` or
+   `deny`) plus a list of channel and
+   port identifiers. If policy is `allow`, then packet relaying will be restricted to this
+   list for the corresponding chain. If the policy is `deny`, then any packets
+   from this list will be ignored.
+
+#### Added filtering based on client state
+
+The global `filter` option additionally enables filtering of all activities
+based on client state trust threshold. If enabled, Hermes will ignore all
+activity for clients that have a trust threshold different than `1/3`.
+
+#### Added a packet clearing configuration option
+
+This will enable the parametrization of the frequency
+at which Hermes will clear pending packets. This is a global option, called
+`clear_packets_interval`, which applies to all chains in the configuration.
+
+
+The full list of changes is described below.
 
 ### FEATURES