@matthew It could work for me if we stay within this kind of time frame. However, this memory leak problem could affect other users who may not be aware of the problem or the fix. Having an official patch version would be more effective in spreading this fix within the community I think.
—Laureby On Mon, Dec 12, 2022 at 7:36 AM Matthew Topol <m...@voltrondata.com.invalid> wrote: > @Laurent: Would it be sufficient if we cherry-pick the bugfixes to a branch > off of the v10 release and then you can use a replace directive in the > go.mod to point at that particular commit until the v11 release comes out > in 4 - 6 weeks (give or take given the end of year holidays)? > > --Matt > > On Mon, Dec 12, 2022 at 10:09 AM Matthew Topol <m...@voltrondata.com> > wrote: > > > I'm in favor of this, can someone from the PMC please comment to the > > viability of this? I know we have the v11 release coming up in the next > > month or so and we'd need someone to be the release manager for > performing > > a v10.0.2 patch release. So I'm not sure whether or not this is a viable > > option. > > > > --Matt > > > > On Fri, Dec 9, 2022 at 1:21 PM Laurent Quérel <laurent.que...@gmail.com> > > wrote: > > > >> Hi all, > >> > >> I would like to propose the release of a patch containing the following > >> two > >> PRs: > >> - https://github.com/apache/arrow/pull/14892 > >> - https://github.com/apache/arrow/pull/14904 > >> > >> The first one fixes a memory leak issue when the built-in compression is > >> enabled. > >> The other one fixes an issue with empty map. > >> > >> Thanks to Matt Topol for fixing these two bugs quickly. > >> > >> I am currently working on a use of Apache Arrow in the Open Telemetry > >> project. A first beta is planned in December, so I would like to have an > >> official patch (see this repo for more details > >> https://github.com/f5/otel-arrow-adapter) > >> > >> --Laurent Quérel > >> > > > -- Laurent Quérel
