From ed140f157e1bf70182dfb94e885a078d603dedd5 Mon Sep 17 00:00:00 2001 From: Archana Shinde Date: Wed, 19 Feb 2020 17:53:18 -0800 Subject: [PATCH] releases: Update release cadence Update release doc to mention that patch releases are not made every 3 weeks, while minor releases are made every 12 weeks now. Signed-off-by: Archana Shinde --- Stable-Branch-Strategy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Stable-Branch-Strategy.md b/Stable-Branch-Strategy.md index e5052f577..b809fe1ae 100644 --- a/Stable-Branch-Strategy.md +++ b/Stable-Branch-Strategy.md @@ -80,7 +80,7 @@ stable and master. While this is not in place currently, it should be considered ### Patch releases -Releases are normally made every other week for patch releases, which include a GitHub release as +Releases are made every three weeks, which include a GitHub release as well as binary packages. These patch releases are made for both stable branches, and a "release candidate" for the next `MAJOR` or `MINOR` is created from master. If there are no changes across all the repositories, no release is created and an announcement is made on the developer mailing list to highlight this. @@ -94,8 +94,8 @@ If there is urgent need for a fix, a patch release will be made outside of the p ### Frequency Minor releases are less frequent in order to provide a more stable baseline for users. They are currently -running on a six week cadence. As the Kata Containers code base matures it is expected this will become -a much longer duration. The release schedule can be seen on the +running on a twelve week cadence. As the Kata Containers code base has reached a certain level of +maturity, we have increased the cadence from six weeks to twelve weeks. The release schedule can be seen on the [release rotation wiki page](https://github.com/kata-containers/community/wiki/Release-Team-Rota). ### Compatibility