[TRACKING] Libs `0.23.0` and drivers `9.1.0+driver` releases

[ekoops]

As already shared during latest community call, we are nearing a libs (+ driver) release.

During this period the rationale is that no new-feature PRs are allowed to be merged (apart from exceptions). We will use this time to test the libraries before opening the release branch and tagging the code. Any help in testing is always welcome! :)

This issue will be kept up to date with further changes.

See https://github.com/falcosecurity/libs/blob/master/release.md for an explanation of the release process.

Release Phases

Preparation

• Tag all necessary PRs and issues with 0.23.0 and 9.1.0+driver milestones
• Move unfinished work to 0.24.0, next-driver and TBD milestones

Code freeze

• Freeze the code

Release branch

• Create the release branch release/0.23.x
• Open PR on test-infra repository to set the newly created branch as protected 👉 chore(config): protect libs release/0.23.x branch test-infra#1944
• Create release candidate tags and releases on the release branch, for testing purposes
  • Create libs 0.23.0-rc1 tag and release 👉 https://github.com/falcosecurity/libs/releases/tag/0.23.0-rc1
  • Create libs 0.23.0-rc2 tag and release 👉 https://github.com/falcosecurity/libs/releases/tag/0.23.0-rc2
  • Create drivers 9.1.0-rc1+driver tag and release 👉 https://github.com/falcosecurity/libs/releases/tag/9.1.0-rc1%2Bdriver

Testing

• Test the libraries and drivers

Thaw

• Thaw the repo allowing new PR to be merged in the master branch again

Release

• Create libs 0.23.0 tag and release 👉 https://github.com/falcosecurity/libs/releases/tag/0.23.0
• Create driver 9.1.0+driver tag and release 👉 https://github.com/falcosecurity/libs/releases/tag/9.1.0%2Bdriver

[poiana]

There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ekoops]

Next driver version will be 9.1.0+driver as in the development cycle that is ending we have bumped the minor in SCHEMA_VERSION 👉 #2735

[ekoops]

Milestones 0.23.0 and 9.1.0+driver are completed at the moment. Code freeze reached, Opening the release branch release/0.23.x.

[ekoops]

release/0.23.x created. Opening PR on test-infra to set it as protected.

[ekoops]

falcosecurity/test-infra#1944 merged. Creating release candidate 0.23.0-rc1 for testing purposes.

[ekoops]

Release candidate created for libs: https://github.com/falcosecurity/libs/releases/tag/0.23.0-rc1
Release candidate created for drivers: https://github.com/falcosecurity/libs/releases/tag/9.1.0-rc1%2Bdriver

[ekoops]

Created PR to sync Falco with the two new -rc1 release candidates: falcosecurity/falco#3758

[ekoops]

Issue with sinsp_parser::ppm_cmsg_nxthdr() identified and fixed in #2764
PR cherry-picking the fix from master: #2767

[ekoops]

Cherry-picking PR (#2767) merged.
Creating release candidate 0.23.0-rc2 for testing purposes.

[ekoops]

Created libs release candidate 0.23.0-rc2: https://github.com/falcosecurity/libs/releases/tag/0.23.0-rc2

[ekoops]

Created PR to sync Falco with the new 0.23.0-rc2 libs release candidate: falcosecurity/falco#3759