mozilla / mozilla/experimenter
Configure manifesttool to support application field
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 151
- Forks
- 229
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 212
Description
The schemas already know about the application field – now we will need to map each (Feature, Application) pair to a new feature config in Experimenter.
We probably don’t want to do this for all historic versions and should instead have a version cutoff of current release - 2 (or something similar).
┆Issue is synchronized with this Jira Task
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
Start by locating manifesttool and the existing schema handling for the application field. Trace how (Feature, Application) pairs become Experimenter feature configs, then clarify the release-minus-two cutoff and historic-version behavior before implementation. Done means supported mappings are configured without unexpectedly changing older versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100