From ea3a799eab4a5501dd54a71e8617f28738f75a4d Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 19 Jun 2024 22:06:44 -0600 Subject: [PATCH] Patch releases just aren't a good idea --- meta/releasing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/releasing.md b/meta/releasing.md index c0d494e7..eb2c16b7 100644 --- a/meta/releasing.md +++ b/meta/releasing.md @@ -113,8 +113,8 @@ release. Patch releases are used to fix the most recent release on record. Typically a patch release will be deployed if there is an issue with the build machinery, a factual error is introduced by the release, or there are notable clarity issues introduced -by the release which may affect implementation. In all cases, patch releases should -*not* be used if more than 2-4 weeks have passed since the release. +by the release which may affect implementation. It's usually not a good idea to +ship a patch release if it can be avoided. Typos and similar do not generally require a patch release.