Automate the Release Process
- 主要语言
- Java
- 星标
- 3.1k
- 派生
- 1.6k
- 平均合并
- 3 天 12 小时
- 30 天内合并 PR
- 33
描述
## Summary
The current release process relies on `maven-release-plugin` and manual Nexus UI interactions, which is fragile, hard to recover from on failure, and difficult to reproduce consistently across release managers. Some Apache projects like Polaris have moved away from this approach toward scripted, CI-integrated release workflows.
This issue proposes adding a semi-automated release pipeline that which uses ASF provided secrets, SVN users and Nexus Users and is triggered by committers or PMC members while going through manual vote steps.
## Prior Art
- [Apache Polaris semi-automated release guide](https://polaris.apache.org/community/release-guides/semi-automated-release-guide/)
- [Apache Iceberg release scripts](https://github.com/apache/iceberg/tree/main/dev)
### Component(s)
Build
贡献指南
这个仓库没有索引到贡献指南
调研方向
首先审查当前的 maven-release-plugin 工作流,以及 issue 中描述的 Nexus UI 手动操作步骤。对比 Apache Polaris 发布指南和 Apache Iceberg 发布脚本,以确定所需的 ASF secrets、SVN 和 Nexus 用户、由提交触发的步骤以及手动投票环节。完成的标准是:为 committer 或 PMC 成员定义并集成一个可复现的半自动发布流水线。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- build-system, ci-cd, release
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 冷清
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100