From 1500e748443f24868ddf6c259a7e6a7d45ec6779 Mon Sep 17 00:00:00 2001 From: Leo Di Donato Date: Thu, 1 Oct 2020 12:41:59 +0200 Subject: [PATCH] docs: release candency Signed-off-by: Leonardo Di Donato Co-authored-by: Leonardo Grasso --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 31df982f..0987e3e7 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -4,7 +4,7 @@ Our release process is mostly automated, but we still need some manual steps to Changes and new features are grouped in [milestones](https://github.com/falcosecurity/falco/milestones), the milestone with the next version represents what is going to be released. -Releases happen on a bi-monthly cadence ([as per community discussion](https://github.com/falcosecurity/community/blob/master/meeting-notes/2020-09-30.md#agenda)), and we need to assign owners for each (usually we pair a new person with an experienced one). Assignees and the due date are proposed during the [weekly community call](https://github.com/falcosecurity/community). Note that hotfix releases can happen as soon as it is needed. +A release happens every two months ([as per community discussion](https://github.com/falcosecurity/community/blob/master/meeting-notes/2020-09-30.md#agenda)), and we need to assign owners for each (usually we pair a new person with an experienced one). Assignees and the due date are proposed during the [weekly community call](https://github.com/falcosecurity/community). Note that hotfix releases can happen as soon as it is needed. Finally, on the proposed due date the assignees for the upcoming release proceed with the processes described below.