[TRACKING] Libs Release

[FedeDP]

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 PR with milestones 0.10.0 and 4.0.0+driver

Code freeze

• Test the libraries and drivers

Release branch

• Craft release branch
• Release candidate tags should be created in the release branch for testing purposes.
• open in our test-infra repository a PR to set the newly created branch as protected -> update(config): set libs release/0.10.0 branch as protected. test-infra#919

Thaw

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

Final tags

• craft them at the end of the release process

[FedeDP]

Note: next driver version will be 4.0.0+driver, bumping major, because we bumped driver maj API version: #709

[FedeDP]

We reached code freeze; milestones 0.10.0 and 4.0.0+driver are completed at the moment.
I will open a release branch soon.

[FedeDP]

Release branch is now up. The test-infra PR to set the new branch as protected has been opened: falcosecurity/test-infra#919

I will tag RCs soon, and port them to Falco.

[FedeDP]

RC1 tags created: https://github.com/falcosecurity/libs/tags

[FedeDP]

Falco PR to bump to RCs is alive: falcosecurity/falco#2302

[FedeDP]

Some small fixes have been/are being fixed; nothing too worrisome, just minor things.
Otherwise, tests on Falco are going great, libs seem pretty solid!

[FedeDP]

A sync PR has been opened: #796.
This will lead us to 0.10.0 final tag.

[FedeDP]

Final tags are up 😄

• 4.0.0+driver -> https://github.com/falcosecurity/libs/releases/tag/4.0.0%2Bdriver
• 0.10.0 -> https://github.com/falcosecurity/libs/releases/tag/0.10.0

I declare master branch thaw 🚀

[FedeDP]

We can close the tracking issue now :)

/close

[poiana]

@FedeDP: Closing this issue.

In response to this:

We can close the tracking issue now :)

/close

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/test-infra repository.

[FedeDP]

/reopen

We will need a 0.10.1 release :)

[poiana]

@FedeDP: Reopened this issue.

In response to this:

/reopen

We will need a 0.10.1 release :)

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/test-infra repository.

[FedeDP]

The new release branch release/0.10.x is up; it is being set as protected in falcosecurity/test-infra#945.

PR to sync new release branch is #827.
We should not need a new driver tag.

[FedeDP]

Old release/0.10.0 branch has been resetted to the 0.10.0 tag.

[FedeDP]

New tag available: https://github.com/falcosecurity/libs/releases/tag/0.10.1
/close

[poiana]

@FedeDP: Closing this issue.

In response to this:

New tag available: https://github.com/falcosecurity/libs/releases/tag/0.10.1
/close

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/test-infra repository.