Allen Bai

STATUS: - Built on top of https://github.com/coreos/fedora-coreos-pinger/pull/35, in the main function, to create a Daemon process, one process is forked and parent process is immediately terminated. Two threads are then...

cc @lucab @bgilbert

Updated with a `component` field instead of enforcing naming convention. Currently thought on `component` is to support four types of components: `[Custom Project Name] | general | bugfix | security`.

Updated the `component` to allow either `[Project Name]` or `miscellaneous`.

@dustymabe I formatted the doc a little bit and added an example for the intermediate `release-notes.yaml` file that consists a `next-release` field (https://github.com/coreos/fedora-coreos-config/pull/550/files#diff-501cdb98b3adaa694d31c5775aa02a46R14-R29), could you take another look?

Simplified `README.md` and squashed commits.

> Were you planning to just ignore that file in the code? @dustymabe Yes, I was writing the releng code such that: - empty files are ignored - note item...

Will open another PR to `next-devel`, thanks for the reminder! EDIT: Opened https://github.com/coreos/fedora-coreos-config/pull/570

> This still waits for all deployments to be ready, and then once the failed job is the last thing we're waiting for Yes because the ResourceList ordering: https://github.com/helm/helm/blob/main/pkg/kube/wait.go#L54 Test...

I can reproduce the behavior on: `version.BuildInfo{Version:"v3.7.1", GitCommit:"1d11fcb5d3f3bf00dbe6fe31b8412839a96b3dc4", GitTreeState:"dirty", GoVersion:"go1.16.6"}`, Cloud Provider/Platform (AKS, GKE, Minikube etc.): Minikube. Steps to reproduce: - `helm create issue-10279` - Modify `tests/test-connection.yaml` with above job...