Dropping the `Current` aliases

未关闭
#2,680 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, dockerfile, nodejs
领域
devops

调研方向

The current tag aliases are generated by the image build and publishing scripts in the repository, so start with the template or generation logic that emits the current-* and plain current tags. The thread asks maintainers for usage metrics before deciding, so this is a policy question rather than a code change a newcomer can finish alone. Done means a documented decision on deprecating or removing the current tags and, if approved, the matching generator change.

由索引模型根据 Issue 内容生成。

描述

build process

Problem

The concept of the Current release is changing with the changes of LTS/Alpha starting in v27.
The current-* are equivalent to the variant tags. EX: current-alpine3.23 is the same as alpine3.23.
The only gap with that is there is no plain debian that the plain current points to, only the named Debian codename tags like trixie

Solution

Drop/or deprecate the current tags.

Alternatives to Consider

@tianon @yosifkit @LaurentGoderre could you see the metrics on your side for how often these alias are used? If there is significant usage, maybe this would require more effort. If the usage is minimal, we could probably do it sooner. I would guess it wouldn't be zero no matter what, as I assume there are mirrors that are sucking in everything.

主要语言
Dockerfile
星标
8.6k
派生
2k
平均合并
18 小时 12 分钟
30 天内合并 PR
23

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nodejs/docker-node 的其他 Issue

查看 nodejs/docker-node 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。