Even though we do not follow release schedule, I think that it is worth
adding a note about bugfix releases - there is really no reason to delay
them most of the time, as soon as we have new commits on bugfix.

What do you think about the attached patch?

>From e27e05c48a8f36e3c3333322f0b5a4881d63361a Mon Sep 17 00:00:00 2001
Message-ID: <e27e05c48a8f36e3c3333322f0b5a4881d63361a.1702207553.git.yanta...@posteo.net>
From: Ihor Radchenko <yanta...@posteo.net>
Date: Sun, 10 Dec 2023 12:25:07 +0100
Subject: [PATCH] org-maintenance.org: Add a note about frequent bugfix

* org-maintenance.org (For bugfix releases): Clarify that bugfix
releases can be done any time there are new fixes on bugfix branch.
 org-maintenance.org | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/org-maintenance.org b/org-maintenance.org
index bc488f1f..23e6c377 100644
--- a/org-maintenance.org
+++ b/org-maintenance.org
@@ -270,6 +270,11 @@ *** For bugfix releases
 When doing a bugfix release (and only then), you shoud *NOT* merge the
 =main= branch into the =bugfix= branch.
+Do not hesitate to make new bugfix releases when there are new commits
+in the bugfix branch.  This way, more users on GNU ELPA can benefit
+from the recent bug fixes.  Considering a new bugfix release every two
+weeks or so might be a good idea.
 *** For minor and major releases
 :CUSTOM_ID: minor-major-releases

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Reply via email to