Use different thresholds for suggesting increase underestimated severities
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
We might want to have different thresholds for suggesting moves to S3 or S2 (e.g. 2 duplicates and bug is S4 -> suggest moving to S3, 4 duplicates -> suggest moving to S2).
Wdyt @calixteman?
Originally posted by @marco-c in https://github.com/mozilla/relman-auto-nag/pull/1320#discussion_r826825463
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 Python logic that suggests severity increases and read the discussion in relman-auto-nag PR 1320. Confirm how duplicate counts and current severities map to suggestions; done means implementing separate thresholds for S3 and S2 based on duplicate counts, with the proposed cases covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100