You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Laurent Quérel <la...@gmail.com> on 2022/12/09 18:19:26 UTC
Request for Patch release of 10.0.2
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
Re: Request for Patch release of 10.0.2
Posted by Laurent Quérel <la...@gmail.com>.
@Matt. Thanks and I also wish you a good vacation and a good end of the
year!
--Laurent
On Fri, Dec 16, 2022 at 9:31 AM Matt Topol <zo...@gmail.com> wrote:
> @Laurent: I just merged the patches into the "maint-10.0.x" branch. You
> should be able to use `go mod edit -replace` to point at that branch
> instead of the v10.0.1 version tag and pick up the patches.
>
> Once v11 is released in mid-January, v11 will also contain these fixes and
> you'll be able to remove the "replace" directive. Feel free to open a new
> Github issue if you run into any problems! Thanks for your patience with
> this and I hope you enjoy your holidays and end of the year!
>
> --Matt
>
> On Thu, Dec 15, 2022 at 3:31 PM Laurent Quérel <la...@gmail.com>
> wrote:
>
> > @Matt Thanks
> >
> > On Thu, Dec 15, 2022 at 9:51 AM Matt Topol <zo...@gmail.com>
> wrote:
> >
> > > I've created a PR for the cherry-picked changes here:
> > > https://github.com/apache/arrow/pull/14980
> > >
> > > @Kou or @Neal could one of you take a look and approve the PR before I
> > > merge it? It feels like it should at least get approved by someone
> > before I
> > > merge to the maintenance branch, lol.
> > >
> > > --Matt
> > >
> > > On Thu, Dec 15, 2022 at 11:47 AM Neal Richardson <
> > > neal.p.richardson@gmail.com> wrote:
> > >
> > > > I don't see a problem cherry-picking commits to the maintenance
> > > > branch--seems like that's what it should be for, right?
> > > >
> > > > Neal
> > > >
> > > > On Thu, Dec 15, 2022 at 11:17 AM Matt Topol <zo...@gmail.com>
> > > > wrote:
> > > >
> > > > > @Kou It looks like we're going to just have a branch as an
> > un-official
> > > > > patched version that can solve Laurent's issue until the v11
> release
> > > > > happens in mid-january. While a full v10.0.2 patch release would be
> > > > > preferable, it doesn't seem anyone is available to serve as release
> > > > manager
> > > > > given the proximity to holidays, plus we're just gonna have the v11
> > > > release
> > > > > in a few weeks anyways.
> > > > >
> > > > > So that brings me to the question for everyone I guess, should I
> > > create a
> > > > > new branch? Or should I just cherry-pick the fix as a new commit
> into
> > > the
> > > > > "maint-10.x.x" branch? It feels better to have it as a branch on
> the
> > > > > official repo rather than on a fork.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > On Mon, Dec 12, 2022 at 7:09 PM Sutou Kouhei <ko...@clear-code.com>
> > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm sorry but I can't do this (serve as release manager) in
> > > > > > this month. But I can help a committer or PMC member who
> > > > > > wants to serve as release manager for 10.0.2.
> > > > > >
> > > > > > FYI: ASF says that a committer can serve as release manager:
> > > > > > https://infra.apache.org/release-publishing.html#releasemanager
> > > > > >
> > > > > > A committer can't do some release tasks such as signing and
> > > > > > uploading. I can do them instead as a PMC member.
> > > > > >
> > > > > > Is there a committer or PMC member who wants to serve as
> > > > > > release manager for 10.0.2?
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > --
> > > > > > kou
> > > > > >
> > > > > > In <
> > > CAJDG-VQxsbiFuJNZ1NdX+T0DudhXmuJR4eA6HtVi759Y6E-3+w@mail.gmail.com
> > > > >
> > > > > > "Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022
> > > > 10:09:27
> > > > > > -0500,
> > > > > > Matthew Topol <ma...@voltrondata.com.INVALID> 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.querel@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
> >
>
--
Laurent Quérel
Re: Request for Patch release of 10.0.2
Posted by Matt Topol <zo...@gmail.com>.
@Laurent: I just merged the patches into the "maint-10.0.x" branch. You
should be able to use `go mod edit -replace` to point at that branch
instead of the v10.0.1 version tag and pick up the patches.
Once v11 is released in mid-January, v11 will also contain these fixes and
you'll be able to remove the "replace" directive. Feel free to open a new
Github issue if you run into any problems! Thanks for your patience with
this and I hope you enjoy your holidays and end of the year!
--Matt
On Thu, Dec 15, 2022 at 3:31 PM Laurent Quérel <la...@gmail.com>
wrote:
> @Matt Thanks
>
> On Thu, Dec 15, 2022 at 9:51 AM Matt Topol <zo...@gmail.com> wrote:
>
> > I've created a PR for the cherry-picked changes here:
> > https://github.com/apache/arrow/pull/14980
> >
> > @Kou or @Neal could one of you take a look and approve the PR before I
> > merge it? It feels like it should at least get approved by someone
> before I
> > merge to the maintenance branch, lol.
> >
> > --Matt
> >
> > On Thu, Dec 15, 2022 at 11:47 AM Neal Richardson <
> > neal.p.richardson@gmail.com> wrote:
> >
> > > I don't see a problem cherry-picking commits to the maintenance
> > > branch--seems like that's what it should be for, right?
> > >
> > > Neal
> > >
> > > On Thu, Dec 15, 2022 at 11:17 AM Matt Topol <zo...@gmail.com>
> > > wrote:
> > >
> > > > @Kou It looks like we're going to just have a branch as an
> un-official
> > > > patched version that can solve Laurent's issue until the v11 release
> > > > happens in mid-january. While a full v10.0.2 patch release would be
> > > > preferable, it doesn't seem anyone is available to serve as release
> > > manager
> > > > given the proximity to holidays, plus we're just gonna have the v11
> > > release
> > > > in a few weeks anyways.
> > > >
> > > > So that brings me to the question for everyone I guess, should I
> > create a
> > > > new branch? Or should I just cherry-pick the fix as a new commit into
> > the
> > > > "maint-10.x.x" branch? It feels better to have it as a branch on the
> > > > official repo rather than on a fork.
> > > >
> > > > Thoughts?
> > > >
> > > > On Mon, Dec 12, 2022 at 7:09 PM Sutou Kouhei <ko...@clear-code.com>
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I'm sorry but I can't do this (serve as release manager) in
> > > > > this month. But I can help a committer or PMC member who
> > > > > wants to serve as release manager for 10.0.2.
> > > > >
> > > > > FYI: ASF says that a committer can serve as release manager:
> > > > > https://infra.apache.org/release-publishing.html#releasemanager
> > > > >
> > > > > A committer can't do some release tasks such as signing and
> > > > > uploading. I can do them instead as a PMC member.
> > > > >
> > > > > Is there a committer or PMC member who wants to serve as
> > > > > release manager for 10.0.2?
> > > > >
> > > > >
> > > > > Thanks,
> > > > > --
> > > > > kou
> > > > >
> > > > > In <
> > CAJDG-VQxsbiFuJNZ1NdX+T0DudhXmuJR4eA6HtVi759Y6E-3+w@mail.gmail.com
> > > >
> > > > > "Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022
> > > 10:09:27
> > > > > -0500,
> > > > > Matthew Topol <ma...@voltrondata.com.INVALID> 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.querel@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
>
Re: Request for Patch release of 10.0.2
Posted by Laurent Quérel <la...@gmail.com>.
@Matt Thanks
On Thu, Dec 15, 2022 at 9:51 AM Matt Topol <zo...@gmail.com> wrote:
> I've created a PR for the cherry-picked changes here:
> https://github.com/apache/arrow/pull/14980
>
> @Kou or @Neal could one of you take a look and approve the PR before I
> merge it? It feels like it should at least get approved by someone before I
> merge to the maintenance branch, lol.
>
> --Matt
>
> On Thu, Dec 15, 2022 at 11:47 AM Neal Richardson <
> neal.p.richardson@gmail.com> wrote:
>
> > I don't see a problem cherry-picking commits to the maintenance
> > branch--seems like that's what it should be for, right?
> >
> > Neal
> >
> > On Thu, Dec 15, 2022 at 11:17 AM Matt Topol <zo...@gmail.com>
> > wrote:
> >
> > > @Kou It looks like we're going to just have a branch as an un-official
> > > patched version that can solve Laurent's issue until the v11 release
> > > happens in mid-january. While a full v10.0.2 patch release would be
> > > preferable, it doesn't seem anyone is available to serve as release
> > manager
> > > given the proximity to holidays, plus we're just gonna have the v11
> > release
> > > in a few weeks anyways.
> > >
> > > So that brings me to the question for everyone I guess, should I
> create a
> > > new branch? Or should I just cherry-pick the fix as a new commit into
> the
> > > "maint-10.x.x" branch? It feels better to have it as a branch on the
> > > official repo rather than on a fork.
> > >
> > > Thoughts?
> > >
> > > On Mon, Dec 12, 2022 at 7:09 PM Sutou Kouhei <ko...@clear-code.com>
> wrote:
> > >
> > > > Hi,
> > > >
> > > > I'm sorry but I can't do this (serve as release manager) in
> > > > this month. But I can help a committer or PMC member who
> > > > wants to serve as release manager for 10.0.2.
> > > >
> > > > FYI: ASF says that a committer can serve as release manager:
> > > > https://infra.apache.org/release-publishing.html#releasemanager
> > > >
> > > > A committer can't do some release tasks such as signing and
> > > > uploading. I can do them instead as a PMC member.
> > > >
> > > > Is there a committer or PMC member who wants to serve as
> > > > release manager for 10.0.2?
> > > >
> > > >
> > > > Thanks,
> > > > --
> > > > kou
> > > >
> > > > In <
> CAJDG-VQxsbiFuJNZ1NdX+T0DudhXmuJR4eA6HtVi759Y6E-3+w@mail.gmail.com
> > >
> > > > "Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022
> > 10:09:27
> > > > -0500,
> > > > Matthew Topol <ma...@voltrondata.com.INVALID> 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.querel@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
Re: Request for Patch release of 10.0.2
Posted by Matt Topol <zo...@gmail.com>.
I've created a PR for the cherry-picked changes here:
https://github.com/apache/arrow/pull/14980
@Kou or @Neal could one of you take a look and approve the PR before I
merge it? It feels like it should at least get approved by someone before I
merge to the maintenance branch, lol.
--Matt
On Thu, Dec 15, 2022 at 11:47 AM Neal Richardson <
neal.p.richardson@gmail.com> wrote:
> I don't see a problem cherry-picking commits to the maintenance
> branch--seems like that's what it should be for, right?
>
> Neal
>
> On Thu, Dec 15, 2022 at 11:17 AM Matt Topol <zo...@gmail.com>
> wrote:
>
> > @Kou It looks like we're going to just have a branch as an un-official
> > patched version that can solve Laurent's issue until the v11 release
> > happens in mid-january. While a full v10.0.2 patch release would be
> > preferable, it doesn't seem anyone is available to serve as release
> manager
> > given the proximity to holidays, plus we're just gonna have the v11
> release
> > in a few weeks anyways.
> >
> > So that brings me to the question for everyone I guess, should I create a
> > new branch? Or should I just cherry-pick the fix as a new commit into the
> > "maint-10.x.x" branch? It feels better to have it as a branch on the
> > official repo rather than on a fork.
> >
> > Thoughts?
> >
> > On Mon, Dec 12, 2022 at 7:09 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> >
> > > Hi,
> > >
> > > I'm sorry but I can't do this (serve as release manager) in
> > > this month. But I can help a committer or PMC member who
> > > wants to serve as release manager for 10.0.2.
> > >
> > > FYI: ASF says that a committer can serve as release manager:
> > > https://infra.apache.org/release-publishing.html#releasemanager
> > >
> > > A committer can't do some release tasks such as signing and
> > > uploading. I can do them instead as a PMC member.
> > >
> > > Is there a committer or PMC member who wants to serve as
> > > release manager for 10.0.2?
> > >
> > >
> > > Thanks,
> > > --
> > > kou
> > >
> > > In <CAJDG-VQxsbiFuJNZ1NdX+T0DudhXmuJR4eA6HtVi759Y6E-3+w@mail.gmail.com
> >
> > > "Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022
> 10:09:27
> > > -0500,
> > > Matthew Topol <ma...@voltrondata.com.INVALID> 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.querel@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
> > > >>
> > >
> >
>
Re: Request for Patch release of 10.0.2
Posted by Neal Richardson <ne...@gmail.com>.
I don't see a problem cherry-picking commits to the maintenance
branch--seems like that's what it should be for, right?
Neal
On Thu, Dec 15, 2022 at 11:17 AM Matt Topol <zo...@gmail.com> wrote:
> @Kou It looks like we're going to just have a branch as an un-official
> patched version that can solve Laurent's issue until the v11 release
> happens in mid-january. While a full v10.0.2 patch release would be
> preferable, it doesn't seem anyone is available to serve as release manager
> given the proximity to holidays, plus we're just gonna have the v11 release
> in a few weeks anyways.
>
> So that brings me to the question for everyone I guess, should I create a
> new branch? Or should I just cherry-pick the fix as a new commit into the
> "maint-10.x.x" branch? It feels better to have it as a branch on the
> official repo rather than on a fork.
>
> Thoughts?
>
> On Mon, Dec 12, 2022 at 7:09 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>
> > Hi,
> >
> > I'm sorry but I can't do this (serve as release manager) in
> > this month. But I can help a committer or PMC member who
> > wants to serve as release manager for 10.0.2.
> >
> > FYI: ASF says that a committer can serve as release manager:
> > https://infra.apache.org/release-publishing.html#releasemanager
> >
> > A committer can't do some release tasks such as signing and
> > uploading. I can do them instead as a PMC member.
> >
> > Is there a committer or PMC member who wants to serve as
> > release manager for 10.0.2?
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <CA...@mail.gmail.com>
> > "Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022 10:09:27
> > -0500,
> > Matthew Topol <ma...@voltrondata.com.INVALID> 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.querel@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
> > >>
> >
>
Re: Request for Patch release of 10.0.2
Posted by Matt Topol <zo...@gmail.com>.
@Kou It looks like we're going to just have a branch as an un-official
patched version that can solve Laurent's issue until the v11 release
happens in mid-january. While a full v10.0.2 patch release would be
preferable, it doesn't seem anyone is available to serve as release manager
given the proximity to holidays, plus we're just gonna have the v11 release
in a few weeks anyways.
So that brings me to the question for everyone I guess, should I create a
new branch? Or should I just cherry-pick the fix as a new commit into the
"maint-10.x.x" branch? It feels better to have it as a branch on the
official repo rather than on a fork.
Thoughts?
On Mon, Dec 12, 2022 at 7:09 PM Sutou Kouhei <ko...@clear-code.com> wrote:
> Hi,
>
> I'm sorry but I can't do this (serve as release manager) in
> this month. But I can help a committer or PMC member who
> wants to serve as release manager for 10.0.2.
>
> FYI: ASF says that a committer can serve as release manager:
> https://infra.apache.org/release-publishing.html#releasemanager
>
> A committer can't do some release tasks such as signing and
> uploading. I can do them instead as a PMC member.
>
> Is there a committer or PMC member who wants to serve as
> release manager for 10.0.2?
>
>
> Thanks,
> --
> kou
>
> In <CA...@mail.gmail.com>
> "Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022 10:09:27
> -0500,
> Matthew Topol <ma...@voltrondata.com.INVALID> 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 <la...@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
> >>
>
Re: Request for Patch release of 10.0.2
Posted by Sutou Kouhei <ko...@clear-code.com>.
Hi,
I'm sorry but I can't do this (serve as release manager) in
this month. But I can help a committer or PMC member who
wants to serve as release manager for 10.0.2.
FYI: ASF says that a committer can serve as release manager:
https://infra.apache.org/release-publishing.html#releasemanager
A committer can't do some release tasks such as signing and
uploading. I can do them instead as a PMC member.
Is there a committer or PMC member who wants to serve as
release manager for 10.0.2?
Thanks,
--
kou
In <CA...@mail.gmail.com>
"Re: Request for Patch release of 10.0.2" on Mon, 12 Dec 2022 10:09:27 -0500,
Matthew Topol <ma...@voltrondata.com.INVALID> 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 <la...@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
>>
Re: Request for Patch release of 10.0.2
Posted by Laurent Quérel <la...@gmail.com>.
@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 <ma...@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 <ma...@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 <la...@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
Re: Request for Patch release of 10.0.2
Posted by Matthew Topol <ma...@voltrondata.com.INVALID>.
@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 <ma...@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 <la...@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
>>
>
Re: Request for Patch release of 10.0.2
Posted by Matthew Topol <ma...@voltrondata.com.INVALID>.
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 <la...@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
>