Suggestion: Show potential uplift candidates on "Uplift to Firefox Beta" page
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start at Bugzy’s “Uplift to Firefox Beta” page and review how it currently displays uplift requested, approved, and verified bugs. Compare its query behavior with the linked GeckoView wiki query for potential uplift candidates. Done means the page identifies bugs fixed in Nightly but not fixed or explicitly wontfixed in Beta.
Written by the indexing model from the issue text.
Description
Bugzy's "Uplift to Firefox Beta" page currently shows "Uplift requested", "Uplift approved", and "Uplift verified". A useful bug query I've been using for GeckoView: bug fixes that are potential uplift candidates, i.e. bugs that are:
- Fixed in Firefox Nightly (e.g. status-firefox63 is "fixed" or "verified")
- And not fixed or explicitly wontfixed in Firefox Beta (e.g. status-firefox62 is NOT "fixed", "verified", or "wontfix" i.e. the status flag is one of "---,?,affected,fix-optional").
This query slightly increases bug-handling time because engineers or project managers must maintain the beta status-firefox## status flags for all your bugs, but it catches potential uplifts that might have been overlooked otherwise.
Here's a link to the GeckoView wiki's bug query for uplift candidates:
https://wiki.mozilla.org/Mobile/GeckoView/Bugs#Focus.2BGeckoView_Uplifts
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from mozilla/bugzy
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
[FR] Add qe-verify flag tag on recently closed bugs under "My Bugs'May be free again @mimizillaa claimed this 871 days ago, and no pull request is open. Openenhancement
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
solana-foundation/solana-com#2245 ·
Maintainers usually reply within 1 day
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TAMULib/fw-registry#543 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
`document.cookie` with `max-age=0` does not delete the cookiePossibly taken @BartInTheField claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
capricorn86/happy-dom#2460 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Seeed-Studio/wiki-documents#5720 · 1 comment ·
Maintainers usually reply within 1 day