From 4de815819f6cb1fd9786fe3807651e7c2f316d94 Mon Sep 17 00:00:00 2001 From: Scott Rigby Date: Thu, 15 Jan 2026 14:17:33 -0500 Subject: [PATCH] Update release policy: cancel scheduled monthly patches in the same month as a major or minor release Signed-off-by: Scott Rigby --- hips/hip-0002.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hips/hip-0002.md b/hips/hip-0002.md index 9585ecc1b..3578ba6fd 100644 --- a/hips/hip-0002.md +++ b/hips/hip-0002.md @@ -34,8 +34,9 @@ Patch releases should be done once a month on the second Wednesday of each month A patch release should be cancelled: - if it falls within one week before the first release candidate (RC1) of an upcoming minor release - if it falls within four weeks following a minor release +- if a major or minor release is scheduled for the same month -As an example, if Helm 3.9.0-rc.1 is scheduled for January 7th, 2022, the expectation is that no patch releases will be cut for Helm 3.8.x after December 31st, 2021. Similarly, if Helm 3.9.0 is released on January 16th, 2022, the expectation is that the 3.9.1 patch release will not be cut before February 13th, 2022. +As an example, if Helm 3.9.0-rc.1 is scheduled for January 7th, 2022, the expectation is that no patch releases will be cut for Helm 3.8.x after December 31st, 2021. Similarly, if Helm 3.9.0 is released on January 16th, 2022, the expectation is that the 3.9.1 patch release will not be cut before February 13th, 2022. And if Helm 4.2.0 is scheduled for May 2026, that month's scheduled Helm 4 patch release will be cancelled. ### Minor releases For minor releases, it is not necessary to aim for dates that are the same every year. Instead, the following is proposed: