microsoft / microsoft/azure-linux-dev-tools
projects need way to enforce pinned upstream dist-git/spec reference
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 27
- Avg merge
- 4d 33m
- Merged PRs (30d)
- 24
Description
For a 'stable' project/distro, all the upstream references should be pinned to a specific date/time or (per-package) dist-git commit hash. This prevents inputs to the stable project build changing over time.
There also should be a mechanism to opt-out (or opt-in) of the upstream pinning for dev work, possibly a (project/distro-wide) parameter in the toml, and/or azldev cmdline param.
--
Imported on behalf of @ddstreet
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 the TOML project or distro configuration and the azldev command-line entry point. Determine where upstream references are resolved and how stable builds are identified; done means the pinning behavior and its development opt-out are specified and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100