[ruby-core:116291] backport version order policy (was: Re: [Ruby master Bug#20150] Memory leak in grapheme clusters)

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 -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/