poiana
commented
1 year ago @FedeDP: The provided milestone is not valid for this repository. Milestones in this repository: [0.35.0, 0.36.0, 0.37.0]
Use /milestone clear to clear the milestone.
In response to [this](https://github.com/falcosecurity/falco/issues/2554):
>## Scheduled to happen: ~2023-05-3
>
>During the community call of 2023-05-17 I proposed myself as a release manager, and together with the other maintainers we plan to release v0.35 as soon as possible.
>
>I Will keep this issue updated with the current status and progress.
>
>## Current Status
>
>- [x] Code freeze in falcosecurity/libs
>- [ ] Code taw in falcosecurity/libs
>- [ ] Release libs 0.11.0
>- [x] Release drivers 5.0.0: https://github.com/falcosecurity/libs/releases/tag/5.0.0%2Bdriver
>- [ ] Code freeze in falcosecurity/falco
>- [ ] Open release branch in Falco
> - [ ] Branch-protect the branch
>- [ ] Code thaw in falcosecurity/falco
>- [ ] Release Falco v0.35.0
>
>## Release Steps
>
>Process is described in [this document](https://github.com/falcosecurity/falco/blob/master/RELEASE.md).
>
>## Release Blocking PRs
>
>
>## Manual Testing Action Items
>
>- [ ] Running Falco on Kubernetes with the official Helm Charts
>- [ ] Running Falco from RPM and DEB artifacts
>- [ ] Running Falco in a container with the official images
>- [ ] Running/fuzzing Falco with multiple event sources active in parallel
>- [ ] Running/fuzzing Falco with variable syscall buffer dimension
>- [ ] Running Falco in all officially-supported architectures (x86_64, ARM64)
>- [ ] Running Falco with the supported drivers (kmod, eBPF, gVisor, trace files)
>- [ ] Test Falco with event generator
>- [ ] Test that plugins are correctly loaded
>- [ ] Test memory and CPU usage (with Valgrind and other tools)
>- [ ] Test latest version of driver loader
>- [ ] Test that k8s metadata enrichment client works as expected
>- [ ] Test that all Falco CLI options work as expected
>- [ ] Check that Falco log messages are correct and consistent
>- [ ] Test that Falco ruleset loading and validation works as expected
>
>## Action Items
>
>- [ ] **Pre-Release**
> - [ ] Milestone: https://github.com/falcosecurity/falco/milestone/29
> - [ ] Sync with new falcosecurity/libs release 0.11.0:
> - [ ] Sync with new falcosecurity/libs driver release 5.0.0:
> - [ ] https://github.com/falcosecurity/falco/pull/2552
> - [ ] Release plugin-sdk-go
> - [ ] Release plugins:
> - [x] Prebuilt drivers publish
> - [x] https://github.com/falcosecurity/test-infra/pull/1151
> - [ ] Changelog
>- [ ] **Release**
> - [ ] Tag
> - [ ] Github Release
>- [ ] **Website**
> - [ ] Create 0.34 snapshot
> - [ ] Protect snapshot branch
>- [ ] **Announcements**
> - [ ] mailing list
> - [ ] slack channel
>- [ ] **Post-Release**
> - [ ] Update helm charts
> - [ ] Archive community call meeting notes:
>
>## Miscs
>
>/milestone 0.53.0
>
>/assign @fededp
>
>/kind documentation
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
FedeDP
incertum
jasondellaluce
Scheduled to happen: ~2023-06-07
During the community call of 2023-05-17 I proposed myself as a release manager, and together with the other maintainers we plan to release v0.35 as soon as possible.
I Will keep this issue updated with the current status and progress.
Current Status
Release Steps
Process is described in this document.
Release Blocking PRs
Manual Testing Action Items
Action Items
Miscs
/milestone 0.35.0
/assign @fededp
/kind documentation