Major releases will be patched as bugs are resolved. These are called “patch” or “point” releases.
Patch releases never include new functionality or major changes.
Patch releases are always explicitly bug fixes. NOT a new functionality.
Reinstalling a major release will automatically install the latest patch release.
Patch releases frequently contain preemptive bug fixes for issues that were found in newer releases.
Note: the decision to back-port to older versions via patch releases is made by GENERAL BYTES based on the severity of the issue (and other factors).
We strongly encourage operators to routinely upgrade to the newest patch release (weekly), and to upgrade to the latest full release at least every two months. This is for security purposes.
Upgrading your server or terminal to the same installed version results in the installation of the latest patch release for that particular version.
For example: sudo /batm/batm-manage upgrade-server 20220311
Note: the version must not contain a dot (or the patch level after the dot)!
EOL abbreviation next to the release version means that the release version already reached End Of Life and there are no new patches planned for this release. It is highly recommended to operate your server only a version that has not reached EOL yet. Operator should be ready to receive emergency security patch that might not be available for EOL marked versions.
LC-345, LC-344 Fixed shared hibernate sessions between threads LC-298 Exchange transactions has been marked as completed even though the balance is null
BATM-5900 Canadian Sanction list - false positive BATM-5894 Bitfinex crypto test doesn't show a correct amount of fiat
BATM-5869 Notifier makes sure every passed entity is managed by entity manager BATM-5865 Avoid sharing DB entity when calling async methods LC-332 Refactored objects passed into threads submitBuyCryptoTransaction-A and submitBuyCryptoTransaction BATM-5820 Gate - added periodical job for cleaning old upgrade packages LC-325 Master log now contains also hibernate session ids.
BATM-5861 The button "update" is missing on the upgrade dialog. LC-339 Hibernate session was used in incorrect thread when reading NotificationPolicy LC-336 storeTransactionRecordCustomData wasn’t correctly handling null in key or value when storing into the database. BATM-5852 Better logging when fiat currency pairs are not updated and master service is shut down
BATM-5856 Cash was associated with a wrong transaction in Banknote History when customer pressed Cancel