Clarify versioning/update policy in the README
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker
- 领域
- devops, documentation, release
调研方向
从 README 和链接的跟踪 issue #2265 开始；审查其中列出的有关 tags、releases、base-image 重建、不可变性、破坏性变更以及 changelog 内容的问题。完成的标准是 README 清楚说明版本和更新策略，包括 production tags、可变引用与半不可变引用、digests 以及一般性建议。
由索引模型根据 Issue 内容生成。
描述
Breadcrumbs for down the road... (Mostly for myself).
- Context
- Docker Official images and what that means
- Base image updates (eco-system rebuilds)
- Nextcloud Server releases (upstream bumps)
- Image releases
- bugs fixes
- enhancements
- upgrades of underlying bits (e.g. a new major PHP or underlying distribution version)
Production Docker tags:
- Upstream supported stables (proposed)
- latest
- previous
- last
- Generic
- stable / production
Tracking this in: #2265
Immutable:
- No such thing technically since what a tag points to can always be changed
- We attempt to make specific tags semi-immutable at the Dockerfile level, but the images themselves referenced by these tags will technically always change automatically whenever the underlying base images (debian, alpine, php) are updated (generally for security). This is a byproduct of how Docker base images and Docker Official images work.
- The only truly immutable option - if you require that - is to reference your images by their digest. The caveat being you're 100% responsible for security updates.
General recommendations:
- Pin your image references to something. Rule of thumb: a major release or one of { latest, previous, last }
- Tagging policy
- latest/previous/last match upstream
- stable/production generally matches ?
- Breaking changes
- ?
- Image versions
- Nextcloud Server versions
- Base image versioning/rebuilding
- Image tags
- Mutable tags
- Rolling tags
- Semo-immutable
- e.g. "29.0.5"
- Digests (immutable/BOM use)
Changelog:
- Release notes (high-level / quick summary)
- Commit log (detailed /
- 主要语言
- Shell
- 星标
- 7.4k
- 派生
- 1.9k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/docker 的其他 Issue
-
1. To develop bug feature: cron image
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 70/100
-
bug docs
难度 1/5 1 小时以内 新手友好度 72/100
-
0. Needs triage bug
难度 4/5 3-5 天 新手友好度 35/100
-
Imagick architecture mismatch (x86_64 vs aarch64) on official arm64 image causes Apache segfaults未关闭0. Needs triage bug
难度 4/5 3-5 天 新手友好度 50/100
相似的 Issue
-
Standalone Unix updater reports success when curl fails (`curl | sh` masks the exit status); Windows path is unaffected可能已有人在做 @akhil9tiet 今天认领。 未关闭bug CLI windows-os
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
ChrisTitusTech/dwm-titus#397 ·
维护者通常 1 天内回复
-
good first issue help wanted language:fr translation
难度 1/5 1-3 小时 新手友好度 88/100
mrvi0/cli-cheatsheet#268 ·