Automatically set status flags for new version based on its previous version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
This issue is based on the autonag feedback survey.
We should do it without sending bugmail, and not for bugs that were wontfix.
We already have a similar thing for regression bugs where the regressed_by field is not empty. The idea here is to do similar things for other bugs. For example, if Fx106 is affected, automatically mark Fx107 as affected once Fx107 is out.
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 existing handling for regression bugs where regressed_by is populated, then trace how new Firefox versions and Bugzilla status flags are processed. Define the affected-to-next-version behavior, excluding wontfix bugs and avoiding bugmail; done means a bug affected in Fx106 is automatically marked affected in Fx107 after release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100