Misc #20422: Bugfix release process

• Status: Closed
• Assignee: -

[masterleep2 (Bill Lipa)]

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.

[jeremyevans0 (Jeremy Evans)]

• Tracker changed from Bug to Misc
• Backport deleted (3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN)

[zeke (Zeke Gabrielse)]

I would also love to see more transparency here. We want to upgrade to 3.3, but we're currently blocked due to https://bugs.ruby-lang.org/issues/20091 and unsure when a patch release will hit.

[matheusrich (Matheus Richard)]

Thanks for bringing this up. I tried to discuss it at the last dev meeting, but I think the core team missed my question.

[hsbt (Hiroshi SHIBATA)]

In speaking about 3.3.1, we are working in progress for that.

Please wait for complete that work.

[PengPengP (Peng Li)]

I want to upgrade to 3.3, but it's blocked due to #20184.

A segfault on low memory system(~256MB).

[hsbt (Hiroshi SHIBATA)]

• Related to Misc #20432: Proposal for workflow changes related to teeny releases added

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Closed

We continue to discuss release process at #20432