HGP-14 [IB] - Release Candidate (staging branch) bug hunt

Category

Initiative Budget

Summary

To improve the quality of each Hummingbot Client Release, we propose to allocate 1,000,000 HBOT tokens to reward the comunity for bug hunting and bug fix, during the staging phase of each monthly Release.

Details

As detailed on the Hummingbot Release cycle, Release Candidates will be moved to the staging branch once all approved PRPs for that release are merged into development.

During this phase, the Release Candidate still needs to be tested for bugs not found during the initial merge of Pull Requests into the development branch.

As a way to improve the quality of each release, this proposal establish the Bug Hunt program, and allocate 1,000,000 HBOT tokens to be distributed as rewards to community members that find and/or fix bugs on the staging branch.

Severity Classification

Each bug will be classified according to the following structure:

NOTE: The list above are examples for reference. Once the bug is reported, Hummigbot Foundation team will evaluate the severity of the bug through internal testing.

Rewards allocation Structure

Community members can request a reward as a Bug Finding and/or a Bug Fix.

The rewards will be allocated of the following structure

Participation Rules

After all approved PRPs are merged and the staging branch is updated as the next Release Candidate, Hummingbot Foundation team will create a Pinned Thread on Commonwealth, detailing what Pull Requests are going into the next release.

Example: Release v1.1 Thread

Once the Release Candidate Thread is created, the Bug Hunt for that release will be active, until the new relase deployment on the main branch is done. Then, the thread for that release candidate will be closed.

To report a bug and/or a bug fix on the release candidate staging branch, the community members must reply to the “Client release candidate staging branch review active” thread using the formats below.

Bug Finding Report

Type: Bug Found

Severity:

Bug Description:

How to reproduce: <Describe the steps to reproduce the bug, with as much details as possible?

Bug Fix Report

Type: Bug Fix <Add Bug Found to the type, if the bug wasn’t reported before>

Severity: . NOTE: Hummingbot Foundation reserved the right to modify the Severity.

Bug Description:

Fix PR: <add a link to the Pull Request targeting the staging branch>

How to reproduce: <Describe the steps to reproduce the bug, with as much details as possible?

Reward payment

Rewards approved by the Hummingbot Foundation team will be sent to the address used to report on the respective staging branch review thread on Commonwealth, after every new release is deployed into the master branch.

Important Notes

• Bug fixes aimed to the staging branch do not need to go through a PRP voting
• Bug fixes reports will only be rewarded if the Foundantion QA approves and merge the respective PR
• Bug findings reports will only be rewarded if Foundation QA is able to reproduce the bug and confirm its existance
• If a bug report/fix is related to a possible leak of users sensitive information we ask the community to reach out the Hummingbot Foundation team directly before posting a report.

Budget Allocation

Allocate 1,000,000 HBOT to reward bug findings and bug fixes for the release candidate