From: "Martin J. Dürst via ruby-core" <ruby-core@ml.ruby-lang.org>
To: Ruby developers <ruby-core@ml.ruby-lang.org>
Cc: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Subject: [ruby-core:116291] backport version order policy (was: Re: [Ruby master Bug#20150] Memory leak in grapheme clusters)
Date: Thu, 18 Jan 2024 12:48:10 +0900 [thread overview]
Message-ID: <e7bb63b4-0bae-4e91-a9d2-19949dd17b1a@it.aoyama.ac.jp> (raw)
In-Reply-To: <redmine.journal-106310.20240118032127.42491@ruby-lang.org>
Hello everybody (but in particular Tomoyuki Chikanaga and Yui Naruse),
On 2024-01-18 12:21, nagachika (Tomoyuki Chikanaga) via ruby-core wrote:
> Issue #20150 has been updated by nagachika (Tomoyuki Chikanaga).
>
> Backport changed from 3.0: UNKNOWN, 3.1: REQUIRED, 3.2: REQUIRED, 3.3: REQUIRED to 3.0: UNKNOWN, 3.1: REQUIRED, 3.2: DONE, 3.3: REQUIRED
I was under the impression that backports of bug fixes had to "trickle
down", i.e. first being applied in the main branch, then 3.3, then 3.2,
and so on (of course unless they were not needed for a specific branch).
The above "3.2: DONE, 3.3: REQUIRED" shows that the backport first
occurred in 3.2, before 3.3.
Can somebody please confirm or restate the actual backport policy now in
effect?
Thanks and regards, Martin.
> ruby_3_2 b4f8623441a8be53b643fed826ba44e933cafd7e merged revision(s) b3d612804946e841e47d14e09b6839224a79c1a4.
>
> ----------------------------------------
> Bug #20150: Memory leak in grapheme clusters
> https://bugs.ruby-lang.org/issues/20150#change-106310
>
> * Author: peterzhu2118 (Peter Zhu)
> * Status: Closed
> * Priority: Normal
> * Backport: 3.0: UNKNOWN, 3.1: REQUIRED, 3.2: DONE, 3.3: REQUIRED
> ----------------------------------------
> GitHub PR: https://github.com/ruby/ruby/pull/9414
>
> String#grapheme_cluters and String#each_grapheme_cluster leaks memory because if the string is not UTF-8, then the created regex will not be freed.
______________________________________________
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 prev parent reply other threads:[~2024-01-18 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 20:41 [ruby-core:116016] [Ruby master Bug#20150] Memory leak in grapheme clusters peterzhu2118 (Peter Zhu) via ruby-core
2024-01-08 23:54 ` [ruby-core:116094] " jeremyevans0 (Jeremy Evans) via ruby-core
2024-01-18 3:21 ` [ruby-core:116288] " nagachika (Tomoyuki Chikanaga) via ruby-core
2024-01-18 3:48 ` Martin J. Dürst via ruby-core [this message]
2024-01-19 8:14 ` [ruby-core:116316] " nagachika (Tomoyuki Chikanaga) via ruby-core
2024-01-22 5:02 ` [ruby-core:116361] " Martin J. Dürst via ruby-core
2024-03-14 16:20 ` [ruby-core:117183] " naruse (Yui NARUSE) 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=e7bb63b4-0bae-4e91-a9d2-19949dd17b1a@it.aoyama.ac.jp \
--to=ruby-core@ruby-lang.org \
--cc=duerst@it.aoyama.ac.jp \
--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).