Cut 0.28.2 release

[maxgio92]

Scheduled to happen: > 2021-05-16, < 2021-06-09

This is a patch release. We can make the release happen as the features are merged.

Release Steps

Process is described in this document: https://github.com/falcosecurity/falco/blob/master/RELEASE.md

Release Blocking Features

• fetch libs and drivers from the new repo #1552
• test-infra #398

Action Items

• Update release documentation (docs(release.md): add blog announcement to post-release tasks #1652)
• Update DBG configurations (test-infra #398)
• Prebuilt drivers publish (Jobs status)
• Pre: Release notes
• Pre: Milestones
• Pre: Changelog update (changelog: add notes for 0.28.2 release #1661)
• Tag
• GH Release
• Meeting-notes (community #138)
• Blog (falco-website #442)
• Send email to cncf-falco-dev mailing list
• Announce in Falco slack channel

Open Questions

/milestone 0.28.2
/assign @maxgio92 @leogr @zuc
/kind documentation

[poiana]

@maxgio92: The label(s) priority/important-soon cannot be applied, because the repository doesn't have them.

In response to this:

Scheduled to happen: > 2021-05-16, < 2021-06-09

This is a patch release. We can make the release happen as the features are merged.

Release Steps

Process is described in this document: https://github.com/falcosecurity/falco/blob/master/RELEASE.md

Release Blocking Features

#1552

Action Items

• Update release documentation
• Changelog update for 0.28.2
• Meeting-notes
• Blog
• Send email to cncf-falco-dev mailing list
• Announce in Falco slack channel

Open Questions

/milestone 0.28.2
/assign @maxgio92 @leogr
/priority important-soon
/kind documentation

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.

[poiana]

@maxgio92: You must be a member of the falcosecurity/maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Falco maintainers and have them propose you as an additional delegate for this responsibility.

In response to this:

Scheduled to happen: > 2021-05-16, < 2021-06-09

This is a patch release. We can make the release happen as the features are merged.

Release Steps

Process is described in this document: https://github.com/falcosecurity/falco/blob/master/RELEASE.md

Release Blocking Features

#1552

Action Items

• Update release documentation
• Changelog update for 0.28.2
• Meeting-notes
• Blog
• Send email to cncf-falco-dev mailing list
• Announce in Falco slack channel

Open Questions

/milestone 0.28.2
/assign @maxgio92 @leogr
/priority important-soon
/kind documentation

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.

[leogr]

Update:

The last PR for cutting 0.28.2 is ready to be reviewed 👇
#1552

TODO:
Since the driver version changed, we should also update the Driver Build Grid configuration in test-infra

[maxgio92]

Thanks @leogr. Updated the checklist in this issue's description.

[maxgio92]

I'm going to prepare DBG configurations test-infra #398

[maxgio92]

/assign @leogr @maxgio92 @zuc

[poiana]

@maxgio92: GitHub didn't allow me to assign the following users: zuc.

Note that only falcosecurity members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @leogr @maxgio92 @zuc

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.

[zuc]

hello 👋

[maxgio92]

Hello @zuc!
As discussed @zuc would want to be the release shadow
/assign @zuc

[maxgio92]

Update:

Drivers have been built with success, not published yet (test-infra #398).

[maxgio92]

Update:

• Release blocking feature Rule updates 2018 08.v1 #398 gots merged
• test-infra #398 approved (building)

[maxgio92]

Update:

• Waiting for building drivers (test-infra #398)

[maxgio92]

Update:

• (test-infra #398) got merged
• Waiting to post-merge jobs to publish prebuilt drivers

[maxgio92]

Update:

• Prebuilt drivers have been published

We can start the release! (I'll start with pre checks)

[maxgio92]

Update:

• Opened PR changelog: add notes for 0.28.2 release #1661 for changelog update

[maxgio92]

Update:

• Changelog changelog: add notes for 0.28.2 release #1661 merged

[maxgio92]

Update:

• community meeting notes #138 merged

[maxgio92]

Update:

• Release hold

[leogr]

We are blocked because cpack is wrongly including gRPC INSTALL targets into packages (note the build-static directory that should not be there) 👇

I'm investigating the problem.

[leogr]

Also:

• git tag removed

[maxgio92]

Do you think @leogr this requires a fix on libs building system?

[leogr]

Do you think @leogr this requires a fix on libs building system?

It's possible, but I would opt for a temporary patch on the Falco side when importing libs, so we will not need to upgrade the driver version again for this release.

[leogr]

Patch ready: #1662
Testing in progress 🚀

[leodido]

Since the Falco 0.29.0 milestone is due on June, 09th...

Would not make more sense to fix this in falcosecurity/libs, update the driver version, and release directly Falco 0.29.0 in 7 days?

[maxgio92]

Cannot the 0.29.0 be postponed? Just a question to have different alternatives in case.

[leodido]

So, we should postpone an official, and with a fixed cadence, Falco release only to release a hotfix version (0.28.2, patch level) that itself needs to patch the current libs and driver versions at build time?

Doesn't sound very correct to me, but that's just my opinion :)

[leogr]

Since the Falco 0.29.0 milestone is due on June, 09th...

Would not make more sense to fix this in falcosecurity/libs, update the driver version, and release directly Falco 0.29.0 in 7 days?

Both options are fine to me.

Do we all agree in dismissing the 0.28.2 in favor of 0.29.0 (due date June 9)?

If so, we have to:

• apply the above fix to falcosecurity/libs
• update the driver version in Falco
• update the changelog
• fix the milestone value for each PR in this release

That's totally fine.

Please confirm!

[maxgio92]

Sorry @leodido I didn't get the point that the 0.29.0 has been actually planned, you're right in my opinion.

In that case I agree with you all to dismiss 0.28.2 in favor of 0.29.0.

[fntlnz]

Closing since we agreeed to cut 0.29.0 directly.
/close

[poiana]

@fntlnz: Closing this issue.

In response to this:

Closing since we agreeed to cut 0.29.0 directly.
/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.