docs(RELEASE.md): switch to 3 releases per year #1711
Conversation
Signed-off-by: Leonardo Grasso <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leogr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| @@ -4,7 +4,9 @@ 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. | |||
|
|
|||
| 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. | |||
| Falco releases are due to happen 3 times per year. Our current schedule sees a new release by the end of January, May, and September each year. Hotfix releases can happen whenever it's needed. | |||
There was a problem hiding this comment.
Should we add some language about what denotes a Hotfix release?
There was a problem hiding this comment.
Hotfix releases can happen whenever it's needed. A Hotfix release can be suggested by anyone, and can be approved by a single maintainer.
There was a problem hiding this comment.
AFAIK, we don't have any process in place that allows only one maintainer to approve (at least 2 maintainers are needed to approve PRs).
So, although I agree it would be better to elaborate more on what a hotfix actually is, I'm not completely sure what we want to document. 🤔
What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This PR updates the
RELEASE.mddoc reflecting the new release cycle as discussed by Falco's maintainers.Starting from now, we plan to release 3 times per year.
Thanks to @fntlnz @leodido @kris-nova @mstemm
/milestone 0.30.0
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: