commit | eefbf8eb688aae357264eb70e41d2b4c43fe3697 | [log] [tgz] |
---|---|---|
author | Myrle Krantz <myrle@apache.org> | Thu Dec 14 12:04:21 2017 +0100 |
committer | Myrle Krantz <myrle@apache.org> | Thu Dec 14 12:04:21 2017 +0100 |
tree | f967723b3b0ab0d7ee9065cb6b34f1ca180535e9 | |
parent | 9fd70a9992e8e187864873148f96b42cc867b01e [diff] |
Added test for the case that rhythm was inactive for a few days and needs to "make up" beats. Because this required changing db data in the test I discovered a locking bug by writing this test. The locking changes I made here may be sufficient to allow for a concurrent deployment of rhythm. Maybe. But that should be tested to be sure.
This project provides a heart beatPublish for other microservices which need to start jobs to be executed once and only once at a defined time.
Mifos I/O is an application framework for digital financial services, a system to support nationwide and cross-national financial transactions and help to level and speed the creation of an inclusive, interconnected digital economy for every nation in the world.
The version numbers follow the Semantic Versioning scheme.
In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.
The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:
1.2.3.BUILD-SNAPSHOT
1.3.5.M.1
1.5.7.RC.2
2.0.0.RELEASE
See LICENSE file.