kubernetes-client/python

Figure out a plan to update release branches automatically

Open

#177 创建于 2017年4月17日

在 GitHub 查看
 (7 评论) (0 反应) (0 负责人)Python (6,225 star) (3,323 fork)batch import
help wantedhelp-neededlifecycle/frozen

描述

Release branches in client-python are following a release branch in kubernetes main repo. If there is a patch for main repo's branch, we should figure out a way to at least detect it, even better create a PR automatically and even much better merge that PR if it is backward compatible.

I would consider this task done if we create a PR automatically. Merging on backward compatibility would be just a plus.

贡献者指南

技术栈
pythongithub actions
领域
devopsci cdrelease
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Kubernetes release processPythonGitHub APICI/CD pipelines
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
First, examine the existing release scripts in the repository, likely in a 'release/' directory or CI config files. Understand how release branches are currently managed in both the main kubernetes repo and this client repo. Then propose a solution using GitHub Actions to monitor the main repo's release branch for patches, automatically create PRs with appropriate changes, and potentially merge if backward compatible.