Add release candidates
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
- To encourage wider use of new Server releases
- To ease use of RCs by micro-services Docker users
- To get feedback before final releases are published
This is encouraged per Docker Official documentation.
A variation, rather than publishing via the Official Images path, would be publish these intermediate images via the GitHub Container Registry maybe? https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry
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.
Research direction
Start by reviewing the Docker Official Images publishing path and the linked GitHub Container Registry documentation. The issue does not name repository files, tests, or an implementation entry point; completion would require deciding how release-candidate Server images should be published and identifying a way to gather feedback before final releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100