Introduce Docker versioning
- Dominant language
- Shell
- Stars
- 68
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
[...} New development, quick wins shouldn't be applied to stable version directly. Maybe stable version shouldn't be published from mainstream but from a tag?
You are doing a great work but it is really frustrating having an instance which could stop working at any time when my server pulls again the stable image.
_Originally posted by @valvin1 in https://github.com/friendica/docker/issues/196#issuecomment-1041136954_
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository's current Docker image build and publishing workflow, including how the stable image is produced and tagged. Define a versioning approach that separates development images from stable releases and makes stable tags immutable or release-based; done means users can pull stable images without unexpected changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100