Release Tracking Alert mail contains closed bugs
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
The "Monday Feb 28 -- Release Tracking Alert" contains bugs that are already closed. They might need attention to correct the flags, but are the assignees the right target for this nag?
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 code that generates the Release Tracking Alert and comparing the bugs it includes with their current closed state. Trace how flags and assignees determine the alert recipients; done means the handling of closed bugs and the intended nag audience are clearly defined and covered for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100