mozilla / mozilla/probe-scraper
Fenix release depends on beta channel of browser-engine-gecko
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 73
- Avg merge
- 10h
- Merged PRs (30d)
- 3
Description
cc @fbertsch @mdboom
I noticed that firefox-android-release depends on org.mozilla.components:browser-engine-gecko-beta (with the beta suffix) rather than the release version org.mozilla.components:browser-engine-gecko. Is that intended? If so, we should add a comment to the yaml explaining why. If not, then are we stuck with this dependency for compatibility's sake?
Contributor guide
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 YAML entry defining the firefox-android-release dependency and inspect how its browser-engine-gecko artifact is selected. Confirm whether the beta dependency is intentional or required for compatibility; done means either documenting the rationale in YAML or changing to the release artifact, with validation of the affected release configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, yaml
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100