Add release automation for api, kyaml, cmd/config, and kustomize CLI #5449
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Eschewed features
What would you like to have added?
We need github action definitions for
api
modulekyaml
modulecmd/config
moduleWhy is this needed?
Can you accomplish the motivating task without this feature, and if so, how?
Yes, by following the release documentation on
releasing/README.md
with several manual task. This task simply act as an improvement for current release processWhat other solutions have you considered?
For releasing process, I have considered pure bash scripting as alternative. While it might give flexibility, it's more difficult maintain and less readable. Decided to use Github action instead considering it as current tools used for releasing and can integrate seamlessly with Github features.
For notification feature, I have discussed with the maintainer and we have decided to send the notifications to maintainers' email, considering creating Slack account will require additional wait for action from kubernetes' Slack maintainer. However this decision might change if Github action is not suitable for this feature.
Anything else we should know?
CI/CD design should follow CI/CD best practices, there is no single rule on what best practice is. But generally guides share common characteristics:
I have discussed with the maintainers for the release design and there's a collaboration page as a reference. Please find it here
Feature ownership
The text was updated successfully, but these errors were encountered: