Add product version mapping to specific releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Want to make easier the lookup between a release, e.g DR20 and all the product versions associated with it. This includes pipeline versions, VAC versions, MOS target versions, etc. Consider whether this should live in the tree configs themselves or in a hosted file on the SAS. Could consider use of both, e.g. tree as default + patches in JSON.
This mapping exists in the datamodel product already, and could be migrated. Also provide a convenience function.
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 existing product-version mapping in the datamodel product and reviewing how this repository stores tree configurations. Compare the tree-config and hosted-SAS/JSON options before deciding how to migrate the mapping. Done means releases such as DR20 can look up their pipeline, VAC, MOS target, and other associated product versions through a convenience function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100