Implement some back-off strategy for Intermittent bug closing.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Due to the 3 (or 2) week intermittent bug closing behavior, I'm getting 20-30 mails per week for closing intermittent bugs and 20-30 mails per week for reopening these bugs from the 10 bugzilla components I'm subscribed to.
This is annoying and creates a lot of noise.
Please implement either exponential or linear backoff strategy to reduce the noise of these mails. (time x2 per reopen or time +2 / +3 weeks per reopen).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the intermittent bug closing and reopen-notification logic in the bugbot codebase, then trace how each reopen determines the next closing interval. Clarify whether linear or exponential backoff is intended and verify that repeated reopens produce fewer notification events while the existing closing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100