[ruby-core:117495] [Ruby master Bug#20422] Bugfix release process

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/

Issue #20422 has been updated by 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. ---------------------------------------- Misc #20422: Bugfix release process https://bugs.ruby-lang.org/issues/20422#change-107896 * Author: masterleep2 (Bill Lipa) * Status: Open ---------------------------------------- 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/

Issue #20422 has been updated by matheusrich (Matheus Richard). Thanks for bringing this up. I [tried to discuss it at the last dev meeting](https://github.com/ruby/dev-meeting-log/blob/master/2024/DevMeeting-2024-03-...), but I think the core team missed my question. ---------------------------------------- Misc #20422: Bugfix release process https://bugs.ruby-lang.org/issues/20422#change-107926 * Author: masterleep2 (Bill Lipa) * Status: Open ---------------------------------------- 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/

Issue #20422 has been updated by hsbt (Hiroshi SHIBATA). In speaking about 3.3.1, we are working in progress for [that](https://github.com/ruby/ruby/commits/ruby_3_3/). Please wait for complete that work. ---------------------------------------- Misc #20422: Bugfix release process https://bugs.ruby-lang.org/issues/20422#change-107932 * Author: masterleep2 (Bill Lipa) * Status: Open ---------------------------------------- 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/

Issue #20422 has been updated by PengPengP (Peng Li). I want to upgrade to 3.3, but it's blocked due to #20184. A segfault on low memory system(~256MB). ---------------------------------------- Misc #20422: Bugfix release process https://bugs.ruby-lang.org/issues/20422#change-107936 * Author: masterleep2 (Bill Lipa) * Status: Open ---------------------------------------- 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/

Issue #20422 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Closed We continue to discuss release process at #20432 ---------------------------------------- Misc #20422: Bugfix release process https://bugs.ruby-lang.org/issues/20422#change-107954 * Author: masterleep2 (Bill Lipa) * Status: Closed ---------------------------------------- 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/
participants (5)
-
hsbt (Hiroshi SHIBATA)
-
masterleep2 (Bill Lipa)
-
matheusrich (Matheus Richard)
-
PengPengP (Peng Li)
-
zeke (Zeke Gabrielse)