Seems that bztools does not differenciate the two ESR releases
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
In bug 1180419, Marco was notified with this information:
== Bugs Tracked for ESR31 ==
* https://bugzil.la/1180419 - - (assigned to Marco Bonardo [::mak])
However, the bug was only affecting ESR38 and never ESR31. I guess this tool does not handle correctly the period when we have two ESR releases running in parallel.
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 reproducing the ESR31/ESR38 case described in issue 12 using Bugzilla bug 1180419, then trace the entry point that generates the tracked-bugs report. Check how concurrent ESR releases are distinguished and add coverage for this two-release scenario. Done means the bug appears only under the affected ESR release, not ESR31.
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
- Mostly clear
- Newbie friendliness
- 35/100