From: Ihor Radchenko <yantar92@posteo.net>
To: emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: [PATCH] [WORG] Maintenance: on the frequency of bugfix releases
Date: Sun, 10 Dec 2023 11:28:26 +0000 [thread overview]
Message-ID: <87sf4aqoth.fsf@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
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?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-maintenance.org-Add-a-note-about-frequent-bugfix.patch --]
[-- Type: text/x-patch, Size: 1169 bytes --]
From e27e05c48a8f36e3c3333322f0b5a4881d63361a Mon Sep 17 00:00:00 2001
Message-ID: <e27e05c48a8f36e3c3333322f0b5a4881d63361a.1702207553.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Sun, 10 Dec 2023 12:25:07 +0100
Subject: [PATCH] org-maintenance.org: Add a note about frequent bugfix
releases
* 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
:PROPERTIES:
:CUSTOM_ID: minor-major-releases
--
2.42.0
[-- Attachment #3: Type: text/plain, Size: 224 bytes --]
--
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>
next reply other threads:[~2023-12-10 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 11:28 Ihor Radchenko [this message]
2023-12-10 12:11 ` [PATCH] [WORG] Maintenance: on the frequency of bugfix releases Matt
2023-12-10 12:27 ` Ihor Radchenko
2023-12-10 12:39 ` Matt
2023-12-11 6:29 ` Bastien Guerry
2023-12-11 11:34 ` Ihor Radchenko
2023-12-11 13:46 ` Bastien Guerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf4aqoth.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).