From: "masterleep2 (Bill Lipa) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "masterleep2 (Bill Lipa)" <noreply@ruby-lang.org>
Subject: [ruby-core:117495] [Ruby master Bug#20422] Bugfix release process
Date: Thu, 11 Apr 2024 17:21:29 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20422.20240411172129.52581@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20422.20240411172129.52581@ruby-lang.org
Issue #20422 has been reported by masterleep2 (Bill Lipa).
----------------------------------------
Bug #20422: Bugfix release process
https://bugs.ruby-lang.org/issues/20422
* Author: masterleep2 (Bill Lipa)
* Status: Open
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
I was wondering if it would be possible to have more frequent bug fix releases of the latest stable Ruby. For example, if there was a 3.x.1 available two to three months after 3.x came out, it would make it more appealing to upgrade from a bug safety perspective. Right now there is no bug fix release for 3.3.
I'm not sure what the release process is for bug fix releases - is there any information on this available? I couldn't find any, or any place other than this bug tracker where it seemed like this would be discussed. Sorry if this is the wrong place.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-04-11 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 17:21 masterleep2 (Bill Lipa) via ruby-core [this message]
2024-04-13 20:40 ` [ruby-core:117509] [Ruby master Misc#20422] Bugfix release process zeke (Zeke Gabrielse) via ruby-core
2024-04-16 13:33 ` [ruby-core:117534] " matheusrich (Matheus Richard) via ruby-core
2024-04-16 21:53 ` [ruby-core:117540] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-04-17 1:46 ` [ruby-core:117543] " PengPengP (Peng Li) via ruby-core
2024-04-17 10:07 ` [ruby-core:117556] " hsbt (Hiroshi SHIBATA) via ruby-core
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-20422.20240411172129.52581@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.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.
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).