uplift_beta rule message should not suggest wontfix-ing bugs that are `tracking_firefox_beta +`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
The uplift_beta rule tells developers that their patch landing in nightly and beta is marked affected, and asks them "is this bug important enough to require an uplift?" and suggests they mark the beta status field "wontfix" if it is not. This is wrong if the bug is already being tracked by Release Management (cf_tracking_firefox_beta set to +). If the developer feels the uplift would be a mistake they need to talk to release management and come to a shared agreement.
If the bug doesn't have an explicit tracking "+" or "-" but has a severity of S1 or S2 you probably also don't want to suggest the developer wontfix it without talking to someone about it first.
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
Locate the uplift_beta rule in the Python code and inspect its existing tests or rule entry point first. Trace how tracking and severity fields affect the generated message; done means bugs tracked for Firefox beta, and high-severity bugs without an explicit tracking status, are not given an inappropriate wontfix suggestion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100