v0.5.0

This version is a big step forward previous releases and provides many new features and a better cluster management.

* Now the configuration is fully declarative (see [cluster specification](doc/cluster_spec.md) documentation) ([sorintlab#178](sorintlab#178)).
* Ability to create a new cluster starting from a previous backup (point in time recovery) ([sorintlab#183](sorintlab#183))
 * Wal-e backup/restore example ([sorintlab#183](sorintlab#183))
* Better synchronous replication, the user can define a min and a max number of required synchronous standbys and the master will always block waiting for acknowledge by the required sync standbys. Only synchronous standbys will be elected as new master. ([sorintlab#219](sorintlab#219))
* Production ready kubernetes examples (just change the persistent volume provider) ([sorintlab#215](sorintlab#215))
* To keep an unique managed central configuration, the postgresql parameters can now only be managed only using the cluster specification ([sorintlab#181](sorintlab#181))
* When (re)initializing a new cluster (with an empty db, from an existing instance or from a backup) the postgresql parameters are automatically merged in the cluster spec ([sorintlab#181](sorintlab#181))
* Use only store based communication and discovery (removed all the kubernetes specific options) ([sorintlab#195](sorintlab#195))
* Ability to use TLS communication with the store (for both etcd and consul) ([sorintlab#208](sorintlab#208))
* Better standby monitoring and replacement ([sorintlab#218](sorintlab#218))
* Improved logging ([sorintlab#187](sorintlab#187))

Many other [improvements and bug fixes](https://github.com/sorintlab/stolon/milestone/4)

v0.4.0

Some cleanups and changes in preparation for release v0.5.0 that will receive a
big refactor (with different breaking changes) needed to bring a lot of new
features.

v0.3.0

* Support multiple stores via [libkv](https://github.com/docker/libkv) ([sorintlab#102](sorintlab#102)). Currently etcd and consul are supported.
* Can use pg_rewind to sync slaves instead of doing a full resync ([sorintlab#122](sorintlab#122)).
* The `--initial-cluster-config` option has been added to the `stolon-sentinel` to provide an initial cluster configuration ([sorintlab#107](sorintlab#107)).
* A cluster config option for initializing the cluster also if multiple keepers are registred has been added ([sorintlab#106](sorintlab#106)). By default a sentinel won't initialize a new if multiple keepers are registered since it cannot know which one should be the master. With this option a random keeper will be choosed as the master. This is useful when an user wants to create a new cluster with an empty database and starting all the keeper together instead of having to start only one keeper, wait it to being elected as master and then starting the other keepers.
* The `--discovery-type` option has been added to the `stolon-sentinel` to choose if keeper discovery should be done using the store or kubernetes ([sorintlab#129](sorintlab#129)).
* Various options has been added to the `stolon-keeper` for setting postgres superuser, replication and initial superuser usernames and passwords ([sorintlab#136](sorintlab#136)).
* Numerous enhancements and bugfixes.

Thanks to all the contributors!