kubernetes-client/python

Figure out a plan to update release branches automatically

Open

#177 opened on Apr 17, 2017

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Python (6,225 stars) (3,323 forks)batch import
help wantedhelp-neededlifecycle/frozen

Description

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.

Contributor guide

Tech stack
pythongithub actions
Domain
devopsci cdrelease
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Kubernetes release processPythonGitHub APICI/CD pipelines
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
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.
Figure out a plan to update release branches automatically · kubernetes-client/python#177 | Good First Issue