Author: PHBR0 x58B
Original Post Date: 14 Apr 2022
With the objective to maintain high-quality standards for the Hummingbot Client, whenever a Release Candidate deployed into the
stagingbranch, 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.3
staging branch: GitHub - hummingbot/hummingbot at staging
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
developmentbranch after a final code-review by the Hummingbot Foundation Team.
- Once all approved PRPs are added, the
developmentbranch will be moved to the
stagingbranch, as the release candidate.
stagingbranch can now be tested for bugs and/or any security-related issues before being deployed as a new Client version.
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
stagingbranch should be reported on this thread, to allow all the community to track the issues found.
- Test the
stagingbranch and report on this thread any issues found. (How to run Hummingbot from source);
- Check if all approved PRPs were included on the
stagingmerge. (Look into the closed Pull Requests page on Github);
- Submit a
fixPR 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.
The following PRPs have the respective vote finished before the end of March:
|Title||PRP||Approved?||Added to 1.3 staging?|
|#5130 Fix/Handle no balance for paper connectors in global config||Link||Yes||Yes|
|#5131 Feat/Add CoinFLEX Connector||Link||Yes||Yes|
|#5135 fix / TWAP status order order, order spread||Link||Yes||Yes|
|#5143 feat / order age from creation timestamp||Link||Yes||Yes|
|#5146 Fix/Avellaneda - remove _latest_parameter_calculation_vol||Link||Yes||Yes|
|#5148 fix / Status - Unable to display status output on Windows source and binary||Link||Yes||Yes|
|#5153 Fix/Missing import in AvellanedaMarketMakingStrategy||Link||Yes||Yes|
|#5156 Fix/Avellaneda - TradingIntensity - fix trade sampling||Link||Yes||Yes|
|#5160 feat/allow fees in different tokens||Link||Yes||Yes|
|#5165 fix/user balance failure for time synchronizer||Link||Yes||Yes|
|#5181 feat/add moving_price_band and config on the fly for price_band and price_ceiling||Link||No||No|
|#5183 Fix / binance perpetual order fill amount bug||Link||Yes||Yes|
|#5192 Refactor/AscendEX Connector Update||Link||Yes||Yes|
|#5195 fix / cli handler format string||Link||Yes||Yes|
|#5197 feat/kucoin connector update||Link||Yes||Yes|
Pr #5181 did not meet the minimum quorum as there was more vote that was against rather than for
Hotfixes are urgent Pull Requests are needed to fix high-priority bugs/vulnerabilities before the final release. Thei will be listed on this section, if they are created.