May Release Candidate (1.4) - Staging branch review now active

Author: PHBR0 x58B

Original Post Date: 16 May 2022

With the objective to maintain high-quality standards for the Hummingbot Client, whenever a Release Candidate deployed into the staging branch, Hummingbot Foundation asks the community to test, review and contribute with fixes to that branch before the final release of the month.

This thread lists which Pull Requests have been added to the Release Candidate, and how Hummingbot Community members can contribute to maintain the high quality of every new release.*

RELEASE CANDIDATE 1.4 staging branch: GitHub - hummingbot/hummingbot at staging

Release Proccess Recap

The deployment of a new version of the Hummingbot Client Release run through the following process:

  • Pull Request Proposals approved by the community through governance vote on the PRP Snapshot, will be added to the development branch after a final code-review by the Hummingbot Foundation Team.
  • Once all approved PRPs are added, the development branch will be moved to the staging branch, as the release candidate.
  • The staging branch can now be tested for bugs and/or any security-related issues before being deployed as a new Client version.

Contributing for the quality of a new release

Here are some ways to contribute to maintaining a high quality standard of the Hummingbot Project:

NOTE 1: All reports related to issues found on the staging branch should be reported on this thread, to allow all the community to track the issues found.

  • Test the staging branch and report on this thread any issues found. (How to run Hummingbot from source);
  • Check if all approved PRPs were included on the developmentstaging merge. (Look into the closed Pull Requests page on Github);
  • Submit a fix PR to staging. After creating the Pull Request, add the link on this thread for reference;

NOTE 2: A proposal to reward bug findings/fixing have been approved here. 1 Million HBOT is allocated fof Bug Findings and Bug Fixes. Check the proposal for detaisl on how to participate.

April PRPs

The following PRPs have the respective vote finished before the end of April:

Title PRP Approved? Added to 1.4staging?
#5140 fix/error on install source Link Yes Yes
#5182 fix/ MarketsRecorder error for perpetual funding payments Link Yes Yes
#5194 fix/fix unnecessary text in split order level prompt Link Yes Yes
#5209 fix/rate oracle coingecko prices request Link Yes Yes
#5212 refactor/simplify validation workflow definition Link Yes Yes
#5214 feat / gateway v2 Link Yes Yes
#5215 fix / k2 startup error Link Yes Yes
#5219 Feat/isort Link Yes Yes
#5221 feat/script strategy Link Yes Yes
#5222 fix/xemm decimal invalid operation error when too much quote balance Link Yes No
#5224 Fix/Bybit Perpetual - Multiple bug fixes Link Yes Yes
#5225 Feat/Add CoinFLEX Perpetual Connector Link Yes No
#5227 Fix/TWAP: has_enough_balance() doesn’t consider order amount, but a total target_asset_amount Link Yes Yes
#5233 Feat/Add position mode checks to Perpetual MM and PerpetualTrading base class
Link Yes Yes
#5236 refactor/Use the US spelling of ‘canceled’ and ‘canceling’ Link Yes Yes
#5245 restart gateway when the route /config/update is called Link Yes Yes
#5247 feat/Update CoinAlpha connectors fees schema Link Yes Yes

PR #5222 was not added because there were changes requested in the PR but the developer is busy and cannot accommodate to make the changes

PR #5225 was not added to staging because it still had issues when QA tested it and was not updated in time to make it this release


Hotfixes are urgent Pull Requests are needed to fix high-priority bugs/vulnerabilities before the final release.