Determine microsoft/go-docker update policy for base image changes
Open
Nobody has claimed this yet.
Area-Docker
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
For Windows, we can follow .NET: https://github.com/dotnet/dotnet-docker/blob/main/.github/ISSUE_TEMPLATE/releases/patch-tuesday-release.md
For Linux distros and packages within distros, this needs more investigation.
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 reading the referenced .github/ISSUE_TEMPLATE/releases/patch-tuesday-release.md from dotnet/dotnet-docker and compare its Windows update approach with this repository's Docker setup. Investigate how Linux distribution and package changes should be handled; done means documenting an agreed update policy for Windows and Linux base-image changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100