stackabletech / stackabletech/docker-images
Devise an LTS strategy for our Docker Images
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
Context: For our 22.11 release we wanted to upgrade base images for our older product images. This raised the question of how far back we should do this and whether we should do it for all images etc.
An outcome of this could also be to keep everything updated for now until we find a reason not to do this anymore.
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 reviewing the 22.11 base-image upgrade context and inventorying the older product images in this repository. Determine which images and update timelines the proposed LTS strategy should cover, then document the agreed policy and its scope as the definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100