Open xmudrii opened 1 year ago
I think this is a good idea.
+1
hey, can I work on this? and can you provide the main references to what exactly is needed to get this issue resolved as I am not much experienced in go
but willing to learn more about this and contribute to solving this issue.
hey, can I work on this? and can you provide the main references to what exactly is needed to get this issue resolved as I am not much experienced in
go
but willing to learn more about this and contribute to solving this issue.
@xmudrii any updates on this how can i get started with this ?
@wasup-yash Sorry for delay. I'm on PTO for the next week or two, but I can follow up on this once I'm back.
@wasup-yash Sorry for delay. I'm on PTO for the next week or two, but I can follow up on this once I'm back.
no worries xD
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/milestone v1.31
@dims: The provided milestone is not valid for this repository. Milestones in this repository: [someday
, v1.24
, v1.25
]
Use /milestone clear
to clear the milestone.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale /assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Update: some of the Python scripts might be removed as we consider replacing them with already existing fork-per-release mechanism.
What should be cleaned up or changed:
We have a bunch of Python scripts in
releng/
directory. These scripts are used to handle creating release branch jobs. These scripts also:These Python scripts have several problems:
That said, I think we should consider rewriting these scripts in Go. Additionally, we should consider wrapping everything (config-rotator, config-forker, and existing Python scripts) in a single binary.
Provide any links for context:
See #29387 for more details
/priority important-longterm /sig release cc @kubernetes/release-engineering