Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve our detection of regressions / regression bounty #1570

Open
simonmichael opened this issue Jun 14, 2021 · 1 comment
Open

improve our detection of regressions / regression bounty #1570

simonmichael opened this issue Jun 14, 2021 · 1 comment

Comments

@simonmichael
Copy link
Owner

@simonmichael simonmichael commented Jun 14, 2021

Since hledger aims to be an ultra-dependable tool, I'd like to reduce our rate of regressions (unplanned breakage/changes in things that used to work) being shipped. About 13 have been discovered/reported in the last 6 months. See this mail list thread brainstorming ideas, and also note this bounty proposal:

I'm thinking this would be a great use of our project funds on opencollective: give bounties for new regressions found in master. I will pay $50 for the next regression found (as judged by me, see examples below).

Regressions reported:
https://github.com/simonmichael/hledger/issues?q=label:regression%21 (shortcut: hledger.org/regressions)

Regression bounty instructions:
#1570 (comment) below (shortcut: hledger.org/regressionbounty)

@simonmichael
Copy link
Owner Author

@simonmichael simonmichael commented Jul 9, 2021

Update on the regression bounty:

  • I am claiming the first one myself, for # 1597 !
  • The bounty is now recurring: you can claim it again for new regressions.
  • From this point forward, the amount per regression will be $100 (increased from $50). I'll adjust if it starts getting too expensive.
  • To claim the bounty:
    1. Open an issue
    2. Get it confirmed as a regression by me. (Current definition:
      An unplanned not-good change / I know it when I see it / Like the past examples.)
    3. Submit an expense:
      1. https://opencollective.com/hledger
      2. SUBMIT EXPENSE (if you are logged in, it moves under the ACTIONS menu)
      3. Type: Invoice
      4. Expense title: regression bounty
      5. Description: #issuenumber, optionally with title, or issue url
      6. Amount: $100
    4. Wait for me to approve it
    5. Wait for open collective to pay out (twice a week).

Regression bounties awarded so far:
1.22

1.22.1

@simonmichael simonmichael changed the title improve our detection of regressions improve our detection of regressions / regression bounty Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant