Split publishing on a per-version basis
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
Research direction
The issue names no files, tests, or entry points. Start by tracing how .NET container images and runtime-deps dependencies are currently published, then define how each version can publish independently without delaying servicing or security releases.
Written by the indexing model from the issue text.
Description
Currently publishing of .NET container images is done by publishing all .NET versions together. This is because there can be dependencies amongst the different versions via the runtime-deps base image.
But this is problematic because any issue that pops up for a given .NET version will block publishing as a whole, affecting the publishing of all versions. For example, there have been cases in the past where something was discovered on release day that prevented the release of a Preview version and caused it to be delayed by several days. This would block the publishing of the .NET versions that are in servicing and would impact the release of security fixes. There can be no delay for this. In order to work around this, the preview changes would have to be reverted and all the images rebuilt. This in itself increases the delay of publishing those images that, ideally, should have been unaffected by the issue.
- Dominant language
- Dockerfile
- Stars
- 4.9k
- Forks
- 2k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 28
Contributor 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 dotnet/dotnet-docker
-
area-documentation
Difficulty 1/5 Under an hour Newbie friendliness 68/100
dotnet/dotnet-docker#4597 · 1 reaction ·
-
area-documentation up-for-grabs
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
dotnet/dotnet-docker#2452 ·
-
area-dockerfiles needs-announcement
dotnet/dotnet-docker#7318 · 1 assignee ·
-
untriaged
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/dotnet-docker#7313 · 2 comments ·
-
area-dockerfiles
Difficulty 4/5 3-5 days Newbie friendliness 45/100
dotnet/dotnet-docker#7296 · 6 comments ·
All issues in dotnet/dotnet-docker
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100