Tag stable releases more frequently
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.7k
- Forks
- 336
- PR merge metrics
- No merged PRs in 30d
Description
The most recent tagged release is not up to date with what is included in the current Docker for Mac Stable release. It'd be great if releases could be tagged when commits are considered stable. Without tagged releases the Homebrew version gets out of date. It also makes it hard to figure out a reasonably stable, but up to date, point at which to build the source from.
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 existing release tags and comparing them with the commits included in the current Docker for Mac Stable release. Determine how stable points are identified and how tagging would keep Homebrew and source builds current; done means an agreed, repeatable tagging process is documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, docker
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100