projects need way to enforce pinned upstream dist-git/spec reference
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- build-system
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.
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
- Dominant language
- Go
- Stars
- 18
- Forks
- 29
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 19
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/azure-linux-dev-tools
-
`patch-add` overlay appends `PatchN:` tag at end of preamble instead of grouping with existing Patch tagsPossibly taken @IzanVil claimed this 14 days ago. Openarea: overlays enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/azure-linux-dev-tools#284 · 2 comments ·
Maintainers usually reply within 7 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/azure-linux-dev-tools#374 ·
Maintainers usually reply within 7 days
-
[Bug]: no specification for TOML object modelMay be free again @ddstreet claimed this 40 days ago, and no pull request is open. Openbug
microsoft/azure-linux-dev-tools#318 · 1 comment · 1 assignee ·
Maintainers usually reply within 7 days
-
[Bug]: azldev comp render doesn't always add changelog entriesMay be free again @ddstreet claimed this 52 days ago, and no pull request is open. Openbug GA blocker
microsoft/azure-linux-dev-tools#316 · 1 assignee ·
Maintainers usually reply within 7 days
-
config dump omits per-file overlays and inherited default-component-configPossibly taken @liunan-ms claimed this 52 days ago. Openbug GA blocker
microsoft/azure-linux-dev-tools#264 · 1 assignee ·
Maintainers usually reply within 7 days
All issues in microsoft/azure-linux-dev-tools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
[Bug] Extraction-mode autogen returns pod templates in random order for map-keyed CRDs, so deny and report messages change between runsPossibly taken @ManojLamani claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kyverno/kyverno#17980 · 1 reaction ·
Maintainers usually reply within 1 day
-
raised-by:reviewer
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
medici-finance/assay#2681 ·
Maintainers usually reply within 1 day
-
bug triaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fullsend-ai/fullsend#8353 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
duplication
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openvibely/openvibely#1459 ·
Maintainers usually reply within 2 days