Change dockerupdate to manage preferredMinor/preferredMajor
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
microsoft/go-images started out more complex than it is now, and with less certainty about what we would be supporting. Now, I think adding logic to dockerupdate to assign preferredMinor/preferredMajor to point at the N-1 build would make sense.
This logic could also potentially handle cleanup of old images, because when preferred* changes, that indicates that a new release came out.
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 dockerupdate entry point and any existing handling for preferredMinor or preferredMajor. Determine how image builds identify the N-1 release and whether preferred-tag changes can safely trigger old-image cleanup. Done means the requested tags point to the N-1 build, with cleanup included only if its behavior is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100