-
Notifications
You must be signed in to change notification settings - Fork 239
[DOCS] Clarify ownership and cadence in base image update policy #869
Copy link
Copy link
Closed
Labels
area:docsDocumentation or contributor guide workDocumentation or contributor guide worklevel:beginner20 pts difficulty label for small beginner-friendly PRs20 pts difficulty label for small beginner-friendly PRspriority:mediumImportant issue with normal urgencyImportant issue with normal urgencytype:docsDocumentation work category bonus labelDocumentation work category bonus label
Description
Activity
Metadata
Metadata
Assignees
Labels
area:docsDocumentation or contributor guide workDocumentation or contributor guide worklevel:beginner20 pts difficulty label for small beginner-friendly PRs20 pts difficulty label for small beginner-friendly PRspriority:mediumImportant issue with normal urgencyImportant issue with normal urgencytype:docsDocumentation work category bonus labelDocumentation work category bonus label
Summary
The base image update policy should identify who owns updates and how often checks should run.
Problem
The current documentation is either missing a critical explanation, outdated, or fragmented across too many places.
Where to update
docs/base_image_update_policy.mdExpected outcome
A contributor should be able to complete this update with a focused documentation PR and leave the surrounding docs easier to follow.
Acceptance criteria
Verification
Review the changed docs against the current code paths or scripts they describe and spot-check any commands or file references.
Additional context
Prefer precise edits over broad rewrites unless the referenced section is already structurally broken.