Cut 0.28.1 release

[cpanato]

Scheduled to happen: Tue, 2021-05-04 Fri, 2021-05-21

If all the planned issues are merged before this date we can make the release happen earlier

Release Steps

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

Release Blocking Issues

Action Items

• Update release documentation: urelease/docs: fix link and small refactor in the text #1636
• Changelog update for 0.28.1: changelog: add notes for 0.28.1 release #1645
• Meeting-notes: new(meeting-notes): archiving community calls notes regarding Falco 0.28.1 community#136
• Blog: blog: add blog for Falco release 0.28.1 falco-website#429
• Send email to cncf-falco-dev mailing list
• Announce in Falco slack channel

Open Questions

/milestone 0.28.1
/assign @cpanato @leogr
/priority important-soon
/kind documentation

[poiana]

@cpanato: 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: Tue, 2021-05-04

If all the planned issues are merged before this date we can make the release happen earlier

Release Steps

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

Release Blocking Issues

Action Items

Open Questions

/milestone 0.28.1
/assign @cpanato @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]

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

In response to this:

Scheduled to happen: Tue, 2021-05-04

If all the planned issues are merged before this date we can make the release happen earlier

Release Steps

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

Release Blocking Issues

Action Items

Open Questions

/milestone 0.28.1
/assign @cpanato @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.

[rverma-dev]

Is it possible to start using buildx for multiarch build and release image in dockerhub?

[cpanato]

@rverma-nsl I think this is possible, we can add this topic in the community call and check with all folks. But I can help with this effort for sure.

cc @leogr @leodido @danpopSD

[leodido]

@rverma-nsl indeed

Anyways, there's a previous effort on this topic done in the new/ci-build-aarch64.

The reason it has not been merged was because it required more > 6 hours (hard limit on CircleCI) to complete.

Also,
there is ongoing effort to create a ProwJob to build and ship it.
See here.

Please join the community call (next week, this week it has been canceled because of the KubeCon) :)

We'd gladly take your help!

[leogr]

Hey maintainers,

I know we would like to include #1552 into 0.28.1 but since it's still in progress and blocked by:

• fix(driver/bpf): add missing builtins.h to the install files list libs#38
• API versioning for user/kernel boundary libs#39
• build: upgrade deps and cmakefiles improvements libs#30

that likely needs further testing, I would not risk blocking the release so I moved it to the 0.29.0 milestone.

@falcosecurity/falco-maintainers WDYT?

If that's OK for you, there will be no more open issues for the https://github.com/falcosecurity/falco/milestone/18 so we can proceed with cutting the release.

[cpanato]

If the change in PR #1552 is a feature I agree to move that to 0.29.0. If that is a bug fix we need to evaluate the impact that might have and if that not impact much agree to move

[leodido]

Since #1552 is mentioned in the Falco graduation proposal and 0.29.0 is scheduled for the usual 18th (June) I'd propose to evaluate a 0.28.2 release.

[leogr]

If the change in PR #1552 is a feature I agree to move that to 0.29.0. If that is a bug fix we need to evaluate the impact that might have and if that not impact much agree to move

AFAIK, there're no relevant bug fixes included in the lastest version of libs, thus another good reason to move #1552 to 0.29.0

[cpanato]

@leodido @leogr What is the decision are we moving forward with v0.28.1 without this issue and schedule a v0.28.2? or move this PR straight to v0.29.0?

[leogr]

Hey @cpanato

My vote goes for:

• release v0.28.1 as is now
• push fetch libs and drivers from the new repo #1552 into v0.28.2 and release as soon as possible (for the reason explained by @leodido here).

[leodido]

Since #1552 is mentioned in the Falco graduation proposal and 0.29.0 is scheduled for the usual 18th (June) I'd propose to evaluate a 0.28.2 release.

I believe my vote is clear :)

To recap:

• 0.28.1 (no "v" prefix please to be coherent with other Falco previous releases)
• 0.28.2 as soon fetch libs and drivers from the new repo #1552 (and other PR related to it in libs) lands
• 0.29.0 is - as per our bi-monthly release process - scheduled on 9th June.

[cpanato]

email sent: https://lists.cncf.io/g/cncf-falco-dev/topic/announcement_falco_0_28_1_is/82656444?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,82656444
blog post: https://falco.org/blog/falco-0-28-1/

all good, closing this issue