Marabunta

+++++++++++++++++++

**Improvements**

* Web server returns status 503 instead of 200
* New option 'web-healthcheck-path'

**Bugfixes**

* Fix backup operation if force_version is set

**Improvements**

* Prevent text from bouncing in maintenance page
* raise an exception if there is duplicate keys in migration file

**Backward incompatible change**

* In the migration yaml file, the ``command`` and ``command_args`` options are
now all merged into ``command``

**Features**

* Backup command and backup's ignore_if are now run in a 'sh' shell so we can
inject environment variables in the commands
* Backup command can now use ``$database``, ``$db_host``, ``$db_port``,
``$db_user``, ``$db_password`` that will be substituted by the current
configuration values

**Bugfixes**

* When starting 2 concurrent marabunta process and the first fail, it releases
the lock and the second would start odoo without actually run the migration.
Now, when the migration lock is released, the other process(es) will recheck
all versions as well before running odoo.

**Documentation**

* Add some high-level documentation

**Features**

* 1st version it's always "setup"

In all projects' usecases the 1st version is always to setup the initial state.
Adopting `setup` as the 1st version makes also easier to squash intermediate version
all in one as the project and its releases grow up.

* Support 5 digits version

Now you can use 5 digits versions as per odoo modules.
For instance: `11.0.3.0.1`. This give us better numbering for patches
and makes versionig withing Odoo world more consistent.
Old 3 digits versions are still supported for backward compat.

Full rationale for above changes available here

9b96aca

* Backup option

Migration allows using a `backup` command in order to perform specific
commands (unless explicitly opted-out) before the migration step.

No backup machinery provided as you are suppose to run your own command
to execute the backup.

**Bugfixes**

* Build Py3 wheel on release

Python3!