Thanks y'all, report has been submitted.
Neal
On Mon, Jul 7, 2025 at 9:35 PM Sutou Kouhei wrote:
> Hi,
>
> I've added some notes about JS/Swift/C#/Skype extractions.
>
>
> Thanks,
> --
> kou
>
> In
> "Re: Arrow board update due soon" o
oss C++, Python, and R. This includes discussions around
> standardized benchmark suites and dashboards to detect regressions
> earlier—motivated in part by recent performance issues observed in Arrow R
> 19.x and 20.x.
>
> On Wed, 2 Jul 2025 at 16:50, Neal Richardson
> wrote:
>
Hi all,
It's time for our quarterly ASF board update again. I haven't gotten the
reminder email yet but know it is coming (whenever the July meeting is),
and to give everyone enough time to provide input on the document, I wanted
to get started. Please have a look at [1] and add any updates you'd l
Congratulations!
Neal
On Tue, Jul 1, 2025 at 7:54 AM Jonathan Keane wrote:
> Welcome and congratulations, Alenka!
>
> -Jon
>
> > On Jul 1, 2025, at 10:38, Raúl Cumplido wrote:
> >
> > The Project Management Committee (PMC) for Apache Arrow has invited
> Alenka
> > Frim to become a PMC member a
Makes sense. If we were concerned about downstream breaking, we could set
an upper limit on feather's pyarrow dependency [1] so that anyone using
that package still would get a working setup. Or maybe that's not worth it
and we could just worry about that if we start seeing bug reports.
Neal
[1]
+1
On Mon, May 19, 2025 at 10:06 PM Ruoxi Sun wrote:
> +1
>
> *Regards,*
> *Rossi SUN*
>
>
> On Mon, May 19, 2025 at 6:48 PM Bryce Mecum wrote:
>
> > +1
> >
> > On Mon, May 19, 2025 at 6:24 PM Sutou Kouhei wrote:
> > >
> > > Hi,
> > >
> > > I would like to propose splitting the Swift implement
I'm happy to help too. Thanks JB for organizing!
Neal
On Mon, May 12, 2025 at 1:20 PM Ruoxi Sun wrote:
> I'm volunteering! Thanks.
>
> *Regards,*
> *Rossi SUN*
>
>
> On Mon, May 12, 2025 at 9:06 AM Shoumyo Chakravorti (BLOOMBERG/ 120 PARK) <
> schakravo...@bloomberg.net> wrote:
>
> > I'd love t
+1 (binding)
On Wed, May 7, 2025 at 5:51 AM David Li wrote:
> +1 (binding)
>
> On Wed, May 7, 2025, at 18:08, Antoine Pitrou wrote:
> > +1 (binding)
> >
> >
> > Le 07/05/2025 à 10:48, Raúl Cumplido a écrit :
> >> Hi,
> >>
> >> I would like to propose splitting the JS implementation and the
> >>
Hi Curt,
I see the Unicode license under Category A (all good!) on [1] so I think
you can just vendor and attribute it. That page may also have other advice
on how to handle it.
Maybe you can reply here with a link to the PR when you vendor it, and
others here can review and make sure it follows t
Hi Raúl,
Thanks for starting this discussion. To be totally clear, is the proposal
also to split JS into a separate repository too, or just releasing
independently?
Neal
On Tue, Apr 15, 2025 at 4:09 AM Raúl Cumplido wrote:
> Hi,
>
> This is a similar discussion to the "[DISCUSS] Split Go releas
Report submitted. Thanks all!
Neal
On Mon, Apr 7, 2025 at 1:26 PM Neal Richardson
wrote:
> Thanks to those who made suggestions on the document. Last call for
> edits--I plan to submit it tomorrow.
>
> Neal
>
> On Tue, Apr 1, 2025 at 3:27 AM Ruoxi Sun wrote:
>
>>
or arrow-rs (it would be great for anyone else
> > who has thoughts to leave them in the doc as well)
> >
> > Andrew
> >
> > On Mon, Mar 31, 2025 at 9:34 AM Neal Richardson <
> > neal.p.richard...@gmail.com>
> > wrote:
> >
> > > Hi
Congratulations!
On Thu, Mar 20, 2025 at 8:16 AM Rok Mihevc wrote:
> Congrats Ian! Well deserved!
>
> On Thu, Mar 20, 2025 at 12:04 PM Alenka Frim
> wrote:
>
> > Congratulations Ian!!
> >
> > V čet., 20. mar. 2025, 11:52 je oseba wish maple >
> > napisala:
> >
> > > Congrats Ian!
> > >
> > > B
Hi all,
It's that time again. I've started a document [1] to collect our notes for
the quarterly board report and have filled in the basic statistics already,
but please have a look and add what you think is important to say in the
"Project activity" section. Remember that the ASF board isn't looki
Awesome, thanks for doing this! I tried out a few queries and was impressed
with what I got back.
Neal
On Fri, Mar 28, 2025 at 2:01 PM Nic Crane wrote:
> Hi folks,
>
> The kapa.ai bot is now live on the dev docs! We're using it to test
> whether
> we can enhance user experience of our documenta
+1
On Fri, Mar 21, 2025 at 5:18 AM Raúl Cumplido wrote:
> +1
>
> happy to try it
>
> El vie, 21 mar 2025 a las 7:42, Jacob Quinn ()
> escribió:
>
> > +1
> >
> > On Thu, Mar 20, 2025 at 10:50 PM Sutou Kouhei
> wrote:
> >
> > > Hi,
> > >
> > > I would like to propose enabling GitHub Discussions o
Congratulations!
On Wed, Mar 19, 2025 at 3:26 PM Kevin Gurney
wrote:
> Congratulations, Rok!
>
> From: Ed Seidl
> Sent: Wednesday, March 19, 2025 3:15 PM
> To: dev@arrow.apache.org
> Subject: Re: [ANNOUNCE] New Arrow PMC member: Rok Mihevc
>
> Congrats Rok! Wel
Congratulations!
On Mon, Mar 17, 2025 at 7:00 AM Ian Cook wrote:
> Congratulations Jacob!
>
> On Mon, Mar 17, 2025 at 05:16 Raúl Cumplido wrote:
>
> > Congratulations Jacob!
> >
> > El lun, 17 mar 2025 a las 9:45, Joris Van den Bossche (<
> > jorisvandenboss...@gmail.com>) escribió:
> >
> > > C
Congratulations!
On Mon, Mar 10, 2025 at 7:50 AM Jacob Wujciak wrote:
> Congrats!
>
> Am Mo., 10. März 2025 um 11:56 Uhr schrieb Alenka Frim <
> frim.ale...@gmail.com>:
> >
> > Congratulations and welcome!
> >
> > V pon., 10. mar. 2025, 11:50 je oseba Rok Mihevc
> > napisala:
> >
> > > Congrats
Hi all,
Passing on a message from the ASF Travel Assistance Committee about the ASF
conference in Beijing later this year. See below.
Neal
---
The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code Asia 2025 are now
open!
We will
Thanks for raising this, Kou. I'm personally torn on this because I see
some of the upsides of splitting R out, particularly at the project's state
of maturity, but it's also not as simple as Rust or Java or others we've
split out in the past because of the hard dependency on the C++ libraries.
It'
Congrats, Bryce!
On Wed, Feb 5, 2025 at 2:09 PM William Ayd
wrote:
> Congrats!
>
> Sent from my iPhone
>
> > On Feb 5, 2025, at 2:51 PM, Ian Cook wrote:
> >
> > Congratulations Bryce!!!
> >
> > Ian
> >
> >> On Wed, Feb 5, 2025 at 2:24 PM Antoine Pitrou
> wrote:
> >>
> >>
> >> Hello,
> >>
> >>
#x27;ve tweaked the wording in the community health section a bit, please
> > review!
> >
> > Regards
> >
> > Antoine.
> >
> >
> > Le 06/01/2025 à 22:45, Neal Richardson a écrit :
> > > Thanks Andrew, and thanks to everyone else who has
> Thank you Neal for starting this process. I added some information about
> the Rust implementation and some headers for other implementations
> (C++/C#/Go, etc)
>
>
>
> On Tue, Dec 31, 2024 at 11:22 AM Neal Richardson <
> neal.p.richard...@gmail.com> wrote:
>
>
Hi folks,
It's that time again: our quarterly board update is due. I've started a
document [1] for us to collaborate on. Please add any highlights you think
are relevant for the board.
Happy new year!
Neal
[1]:
https://docs.google.com/document/d/1TWbUlbcPdIyo0Q_r6jcs-eGJe_8sfat_7RKe-aY2lTk/edit
+1 (binding)
On Fri, Nov 22, 2024 at 4:51 AM Raúl Cumplido wrote:
> +1 (binding)
>
> El vie, 22 nov 2024 a las 10:21, Antoine Pitrou ()
> escribió:
> >
> > +1 (binding)
> >
> > Le 22/11/2024 à 02:31, Sutou Kouhei a écrit :
> > > Hi,
> > >
> > > I would like to propose splitting Java release proc
+1, makes sense to me. Since many of the Arrow libraries are at a more
stable phase of development, it makes sense that they should have a release
process and cadence that matches, and that those that are under active
development should be able to move ahead more freely.
Neal
On Mon, Nov 18, 202
Thanks all! I am grateful for the opportunity to serve you this year. If
there is anything I can do to help at any point, please do not hesitate to
reach out.
Neal
On Wed, Oct 30, 2024 at 2:55 PM Joel Lubinitsky wrote:
> Thanks for all your work Andy, and congrats Neal!
>
> On Wed, Oct 30, 2024
Congratulations!
On Wed, Oct 30, 2024 at 6:20 PM Ian Cook wrote:
> Congratulations Curt! Thanks for all your hard work on the C#
> implementation and on ADBC!
>
> Ian
>
> On Wed, Oct 30, 2024 at 5:56 PM Sutou Kouhei wrote:
>
> > The Project Management Committee (PMC) for Apache Arrow has
> > in
Congratulations!
Neal
On Tue, Oct 22, 2024 at 3:50 PM Ian Cook wrote:
> Congratulations Rossi!
>
> Ian
>
> On Tue, Oct 22, 2024 at 3:37 PM Bryce Mecum wrote:
>
> > Congrats, welcome, and thanks for all the great work so far!
> >
> > On Tue, Oct 22, 2024 at 12:02 PM Weston Pace
> > wrote:
> >
Adam,
Yes, I saw that when it was introduced here, on a PR I did:
https://github.com/apache/arrow/runs/25894658283
It's on the smallest scale factor and on two of the queries (
https://github.com/voltrondata-labs/arrowbench/blob/main/R/tpch-queries.R#L510-L535
and
https://github.com/voltrondata-la
Congratulations!
On Mon, Mar 18, 2024 at 6:45 AM Rok Mihevc wrote:
> Congrats and welcome Bryce!
>
> On Mon, Mar 18, 2024 at 11:07 AM Andrew Lamb wrote:
>
> > Congratulations Bryce!
> >
> > On Mon, Mar 18, 2024 at 3:35 AM Alenka Frim > .invalid>
> > wrote:
> >
> > > Congratulations Bryce and t
Congratulations!
On Mon, Nov 13, 2023 at 3:10 PM Matt Topol wrote:
> Congratulations Raul!!
>
> On Mon, Nov 13, 2023, 3:09 PM Antoine Pitrou wrote:
>
> >
> > Welcome Raul, we're glad to have you!
> >
> > Regards
> >
> > Antoine.
> >
> >
> > Le 13/11/2023 à 20:27, Andrew Lamb a écrit :
> > > The
Nice work!
Neal
On Thu, Oct 19, 2023 at 4:01 PM Antoine Pitrou wrote:
>
> Hello again,
>
> Quick update: the C++, C#, Go and Java implementations now all
> participate in C Data Interface integration testing.
>
> (this helped us fix a few interoperability bugs, and add deterministic
> releasing
Congratulations!
On Sun, Oct 15, 2023 at 1:35 PM Bryce Mecum wrote:
> Congratulations, Jon!
>
> On Sat, Oct 14, 2023 at 9:24 AM Andrew Lamb wrote:
> >
> > The Project Management Committee (PMC) for Apache Arrow has invited
> > Jonathan Keane to become a PMC member and we are pleased to announce
Agreed, it's unfortunately not just a simple tradeoff. We have discussed
this a bit in [1] and in several other threads around this topic. If we say
that Arrow is about interchange and not execution, so we shouldn't adopt
the pointer version that DuckDB uses, that means we're also making
interchang
I would be curious how old that language is in the ASF policy. In the era
of cloud infrastructure and public CI, "your own hardware" might mean
something different than it once did. IMO, it is essential that we download
and test the release artifacts in a separate context from where they are
built
+1
Thanks all for the thoughtful discussions here.
Neal
On Fri, Aug 18, 2023 at 4:14 AM Raphael Taylor-Davies
wrote:
> +1 (binding)
>
> Despite my earlier misgivings, I think this will be a valuable addition
> to the specification.
>
> To clarify I've interpreted this as a vote on both Utf8Vie
Hi all,
As was previously raised in [1] and surfaced again in [2], there is a
proposal for representing alternative layouts. The intent, as I understand
it, is to be able to support memory layouts that some (but perhaps not all)
applications of Arrow find valuable, so that these nearly Arrow system
Since this is now the second time that the proposal of a new type has
raised the "alternative layout" question, I'm going to start a new thread
about that.
Neal
On Wed, Jul 12, 2023 at 11:37 AM Pedro Eugenio Rocha Pedreira
wrote:
> Hi all, this is Pedro from the Velox team at Meta. Chiming in h
Thanks, Joe. Looking forward to seeing this come together.
Neal
On Mon, Jul 3, 2023 at 11:29 AM Joe Marshall
wrote:
> Hi,
>
> I'm a pyodide developer amongst other things (webassembly cpython
> intepreter) and I've got some PRs in progress on arrow relating to
> webassembly support. I wondered
Hi all, checking back in about the patch release. Do we have a timeline for
when we plan to do it? Looks like Weston's PR is about ready to go, and I
believe that was the last outstanding issue.
Neal
On Fri, May 19, 2023 at 5:30 AM Sutou Kouhei wrote:
> Sure!
>
> In
> "Re: [DISCUSS] Interest
Congratulations!
On Wed, May 3, 2023 at 1:58 PM Jacob Wujciak
wrote:
> Congratulations, well deserved!
>
> On Wed, May 3, 2023 at 7:48 PM Weston Pace wrote:
>
> > Congratulations!
> >
> > On Wed, May 3, 2023 at 10:47 AM Raúl Cumplido
> > wrote:
> >
> > > Congratulations Matt!
> > >
> > > El mi
Thanks for following up on this. Just a point of order: I don't think PMC
approval or voting is required to merge to arrow-site. Though I agree that
it's always good to get more eyes on things we publish to the web.
Neal
On Fri, Apr 28, 2023 at 6:33 PM Will Jones wrote:
> Thanks for highlightin
+1, thanks for taking the initiative on this!
Neal
On Mon, Apr 24, 2023 at 6:10 AM Andrew Lamb wrote:
> +1
>
>
> On Mon, Apr 24, 2023 at 1:55 AM David Li wrote:
>
> > +1
> >
> > Thanks Kou!
> >
> > On Mon, Apr 24, 2023, at 11:53, Sutou Kouhei wrote:
> > > +1
> > >
> > > In <20230424.103259.664
+1 (Intel Mac)
Neal
On Wed, Apr 19, 2023 at 1:20 PM Jacob Quinn wrote:
> +1 (macOS M1)
>
> -Jacob
>
> On Tue, Apr 18, 2023 at 1:59 AM Sutou Kouhei wrote:
>
> > Hi,
> >
> > I would like to propose the following release candidate (RC1) of
> > Apache Arrow Julia version 2.5.2.
> >
> > This releas
Or, possibly you're on an older version of R, and CRAN no longer builds
binary packages for your version.
Regardless, CRAN doesn't host binary packages for Linux, and we have no
control over what binaries/versions they do host, so unfortunately there's
nothing the Arrow community can do about what
Congrats, Will!
On Mon, Mar 13, 2023 at 2:37 PM Anja wrote:
> Congrats, Will!! =)
>
> On Mon, 13 Mar 2023 at 11:23, Weston Pace wrote:
>
> > Congratulations Will!
> >
> > On Mon, Mar 13, 2023, 11:22 AM Ian Cook wrote:
> >
> > > Congratulations Will!
> > >
> > > On Mon, Mar 13, 2023 at 1:58 PM
Would it make sense to transfer all governance of the parquet-cpp
implementation to Apache Arrow? It seems like that's where we de facto are
already, so that would resolve these ambiguities and put it in line with
the Rust implementation.
Would the Parquet PMC be opposed to formalizing this change
+1, with or without description
Neal
On Tue, Jan 31, 2023 at 11:04 AM Weston Pace wrote:
> +1 to both. This only applies to the merge button and, in that case, the
> committer has a chance to review the message before merging. So if there
> is garbage in the description hopefully they can cat
> > * Proceed with RC0, fix for 12.0.0 (and 11.0.1, should it happen),
> > and
> > >> > > cherry-pick the fix into the bundle we upload to CRAN for 11.0.0.
> > (This
> > >> > is
> > >> > > something we do regularly, not a cr
Correct, it does. So as long as you base your branch off of the original
contributor's PR, or cherry-pick their commit(s) into yours, the
attribution should show up.
Neal
On Wed, Jan 25, 2023 at 10:54 AM Antoine Pitrou wrote:
>
> Le 25/01/2023 à 16:47, Julian Hyde a écrit :
> > A common practic
I received an email this morning from the CRAN maintainers about a C++
build failure on clang 16. Although clang 16 is not scheduled for release
until March, CRAN wants to ensure that all packages build successfully on
it when it becomes available, so they've given us an ultimatum to fix the
issue
Congratulations!
On Mon, Dec 26, 2022 at 4:38 PM Matt Topol wrote:
> Congrats!!!
>
> On Mon, Dec 26, 2022, 12:47 PM Jacob Wujciak >
> wrote:
>
> > Congratulations Andrew!
> >
> > Matthew Turner schrieb am Mo., 26. Dez.
> > 2022, 16:44:
> >
> > > Congratulations, Andrew!
> > >
> > > From: Yijie
Congrats!
On Thu, Dec 15, 2022 at 7:00 PM Ian Cook wrote:
> Herzlichen Glückwunsch, Jacob!
>
> On Thu, Dec 15, 2022 at 6:56 PM Rok Mihevc wrote:
> >
> > Congrats Jacob!!
> >
> > Rok
> >
> > On Fri, Dec 16, 2022 at 12:52 AM Vibhatha Abeykoon
> > wrote:
> >
> > > Congratulations Jacob!!!
> > >
>
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 wrote:
> @Kou It looks like we're going to just have a branch as an un-official
> patched version that can solve Laurent's iss
Congratulations!
> On Dec 6, 2022, at 6:11 AM, vin jake wrote:
>
> Congratulations Raúl !!
>
>> On Tue, Dec 6, 2022 at 7:11 PM Rok Mihevc wrote:
>>
>> Congrats Raul!!
>>
>>> On Tue, Dec 6, 2022 at 12:04 PM Andrew Lamb wrote:
>>>
>>> Congratulations Raúl
>>>
>>> On Tue, Dec 6, 2022 at 2
ASF Infra is running a survey and would like feedback from any committer.
Cross-posting here in case folks aren't on the infra mailing list. If you
have opinions you would like to share, please see the link below.
Neal
-- Forwarded message -
From: Chris Thistlethwaite
Date: Thu,
> - This creates an immediate need to modify the PR merge script; Raúl
> opened an issue for this after the call [6]; this also raises the
> question of whether we still need the PR merge script or whether
> committers can use the "Squash and merge" button in the GitHub web UI
> instead
>
I think
+1
Verified on Intel macOS 13
Neal
On Thu, Nov 17, 2022 at 9:00 AM Raúl Cumplido
wrote:
> +1
>
> Tested on Ubuntu 22.04.1 LTS
>
> El jue, 17 nov 2022 a las 14:42, David Li ()
> escribió:
>
> > +1 (binding)
> >
> > Tested on AMD64/Linux (Ubuntu 18.04)
> >
> > On Thu, Nov 17, 2022, at 07:18, Eri
Would it be feasible to make it arrow.apache.org/docs/adbc, and nightly
under arrow.apache.org/docs/dev/adbc, for consistency with the rest of the
docs?
Neal
On Tue, Nov 8, 2022 at 8:27 AM David Li wrote:
> Thanks! Yes, I was looking at how the Cookbook works and plan to use the
> same setup. I
Two unrelated thoughts:
1. Since it sounds like we need to do a patch release for the wheels,
should we include any other critical bugfixes that have been reported
affecting 10.0.0? Do we have a 10.0.1 Fix Version in Jira already, and/or
any known issues we would want to include?
2. Since I said "
n Thu, Oct 27, 2022 at 4:25 PM Matt Topol wrote:
> +1 (Non-binding)
>
> On Thu, Oct 27, 2022, 4:19 PM Joris Van den Bossche <
> jorisvandenboss...@gmail.com> wrote:
>
> > +1
> >
> > On Thu, 27 Oct 2022 at 07:27, Jacob Quinn
> wrote:
> > >
&
t; Arrow Jira issues but never created an Arrow PR that was merged.
> >
> > Please do some sanity-checking on this list before using it.
> >
> > [1] https://gist.github.com/ianmcook/0f1538ebc8268a88cd4e0a0a61445287
> > [2]
> https://docs.google.com/spreadsheets/d/1C8Px
I propose that we move issue tracking from the ASF's Jira to GitHub Issues.
This has been discussed on [1] and [2] and there seems to be consensus. A
number of Arrow subprojects already use GitHub Issues; this moves the issue
tracking for `apache/arrow` into GitHub along with the source code.
The
Attendees:
Vibhatha Abeykoon
Raúl Cumplido
James Duong
Sean Gallagher
Ian Joiner
Will Jones
David Li
Antoine Pitrou
Neal Richardson
Matt Topol
Jacob Wujciak
Discussion:
Release 10.0.0: it's done, and it seemed to go smoothly. Kudos to all who
have been working to make releases easier!
to create an issue to track a decision/concern
> that's not already defined.
>
> On Tue, Oct 25, 2022 at 6:37 AM Neal Richardson <
> neal.p.richard...@gmail.com>
> wrote:
>
> > I'll start a vote on this in the next day or so since it seems like we
> have
&
I will submit the R package to CRAN.
Neal
On Wed, Oct 26, 2022 at 4:40 AM Sutou Kouhei wrote:
> Thanks!!!
>
> Current status:
>
> - [Done] Make the released version as “RELEASED” on JIRA
> - [Done] Make the CPP PARQUET related version as “RELEASED” on JIRA
> - [Done] Start the new version on JI
+1
On macOS 12.6 (arm64), Python 3.9.12, I ran:
TEST_DEFAULT=0 TEST_WHEELS=1 dev/release/verify-release-candidate.sh
10.0.0
and it succeeded, but some Python subprocess or something crashed in the
test suite--I think it was around test_pandas or test_plasma but I wasn't
paying close attentio
I'll start a vote on this in the next day or so since it seems like we have
consensus on the main issue (moving from Jira to GitHub Issues) and are
working out the finer points on how we'll migrate and how we'll map Jira
concepts to Issues.
Speaking of the migration: now would be an *excellent* ti
t;
> Hi Neal,
>
> Le 22/10/2022 à 15:35, Neal Richardson a écrit :
> >
> > Their email says:
> >
> >> Infra knows this process change places an increasing burden on PMC
> members
> >> for managing contributors, and makes it harder for people to con
Hi all,
ASF Infra has announced [1] that, due to spam account creation, it will no
longer be possible for people to sign themselves up for a Jira account to
report issues as of November 6. Instead, the PMC will have to request the
creation of Jira accounts.
Their email says:
> Infra knows this pr
On Thu, Oct 20, 2022 at 11:31 AM Jacob Wujciak
wrote:
> This is definitively an important topic that should be discussed. I just
> want to point out that there is no difference between a major, minor or
> patch release with regards to the ASF process. Any official release needs a
> vote and a PMC
+1
(I think this makes 4 binding +1s, if I count correctly)
On Wed, Oct 5, 2022 at 11:30 AM Antoine Pitrou wrote:
>
> +1 (binding), with the caveat that I looked mostly at the C API.
>
> Regards
>
> Antoine.
>
>
> Le 21/09/2022 à 17:40, David Li a écrit :
> > Hello,
> >
> > We have been discuss
On Mon, Sep 12, 2022 at 12:44 PM David Li wrote:
> I like this idea. I would also like to set up some sort of automated ABI
> checker as well (the options I found were GPL/LGPL so I need to figure out
> how to proceed).
>
You should be able to use GPL software in CI, that's no problem. You can
e
+1
Neal
On Thu, Sep 8, 2022 at 2:15 PM Ashish wrote:
> +1 (non-binding)
>
> On Thu, Sep 8, 2022 at 9:41 AM Gavin Ray wrote:
>
> > Oh, so that's what "non-binding" means in vote threads
> > Those threads make a lot more sense now, thanks for the heads-up =)
> >
> > On Thu, Sep 8, 2022 at 12:31
I agree with Micah. Moreover, adding "org.apache" does not disambiguate
anything; "arrow" should be the reserved namespace for canonical
(extension) types.
Neal
On Wed, Aug 24, 2022 at 12:31 PM Micah Kornfield
wrote:
> Sorry for beling late. I'm -0.5 on "org.apache.arrow." given people
> previ
https://cpp11.r-lib.org/articles/motivations.html is a good summary of why
we use cpp11.
Neal
On Fri, Aug 19, 2022 at 1:23 PM Mauricio Vargas Sepúlveda
wrote:
> Hi!
>
> Which was the practical reason to use cpp11 for the R package?
>
> I ask because now I'm in the process of creating a fork of
I have no opinion about the benefits of upgrading to C++17. From the R
perspective, there are a handful of packages on CRAN that require C++14 or
C++17. Last year, when I asked other R package maintainers why they hadn't
upgraded to newer C++ standards, the reasoning was that because many
packages
+1, SGTM
Neal
On Wed, Aug 10, 2022 at 6:17 PM Rok Mihevc wrote:
> It would be great if this friction point is removed. +1
>
> Rok
>
> On Wed, Aug 10, 2022 at 11:36 PM Sutou Kouhei wrote:
>
> > +1
> >
> > In
> > "Proposal: Allow any ASF Jira user to assign ARROW issues" on Wed, 10
> > Aug 20
CRAN is closed for new submissions until August 5, so I'll submit the R
package next week.
On Wed, Aug 3, 2022 at 7:19 AM Krisztián Szűcs
wrote:
> Below is the current status of the post release tasks, I
> "soft-assigned" a couple of them to the relevant maintainers, could
> you please help with
Sounds good to me too. +1 on the canonical extension type option; maybe it
should end up as a first-class type, but I'd like to see us try it without
first and see what that tells us about the path for having an extension
type get promoted to being a first-class type. This is something that has
bee
ng the link to
> >> the previous discussion and creating the umbrella issue/breaking
> >> down the tasks in Jira.
> >>
> >> I am happy to work on these subtasks to move the effort forward;
> >> I’ll start with this subtask [1].
> >>
> >>
+1
Neal
On Thu, Jul 14, 2022 at 5:17 PM Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 8.0.1 0
>
> with:
>
> * go version go1.18.3 linux/amd64
>
>
> Thanks,
> --
> kou
>
>
+1
Neal
On Thu, Jul 14, 2022 at 5:16 PM Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 7.0.1 0
>
> with:
>
> * go version go1.17.11 linux/amd64
>
>
> Thanks,
> --
> kou
>
>
+1. Thank you for doing this, Kou.
Neal
On Thu, Jul 14, 2022 at 5:15 PM Sutou Kouhei wrote:
> +1
>
> I ran the followings on Debian GNU/Linux sid:
>
> * TEST_DEFAULT=0 \
> TEST_GO=1 \
> dev/release/verify-release-candidate.sh 6.0.2 0
>
> with:
>
> * go version go1.18.3 linux/amd
Sounds like a good idea to me, thanks for taking the initiative on this.
To Benson's idea about varying the timeout based on priority, IMO we could
just start with the simple approach and see how that goes. Maybe that would
be helpful but maybe it's not necessary. If you're truly watching an issue
I've enabled the web-public option on https://ursalabs.zulipchat.com/
turned it on for the main discussion streams. Anyone can go to that URL and
not only view discussions in those streams but also sign themselves up to
be able to participate in discussions there.
Neal
On Wed, Jun 29, 2022 at 5:0
One challenge with automatically creating issues is that sometimes a single
cause will make many builds fail (think python wheels or conda packages,
across versions and platforms). So it may end up creating a lot of issues
we have to close as duplicate (and have to track that so we don't re-create
On behalf of the Arrow PMC, I'm happy to announce that
Dewey Dunnington
Alenka Frim
Rok Mihevc
have all accepted invitations to become committers on Apache Arrow!
Welcome, thank you for all your contributions so far, and we look forward
to continuing to drive Apache Arrow forward to an even bette
Personally, I don't have a problem with doing `git tag` just for Go. I
don't think this needs a full patch release process since we aren't
producing new artifacts that need signing, we're only adding a tag that
points to a SHA in git. But I am not an expert in this area of policy and
will defer to
+1
On Wed, Jun 8, 2022 at 7:44 PM Sutou Kouhei wrote:
> +1
>
> In
> "[VOTE] Mark C Stream Interface as Stable" on Wed, 8 Jun 2022 11:15:29
> -0700,
> Will Jones wrote:
>
> > Hi,
> >
> > Given all feedback to discussion [1] has been positive, I would like to
> > propose marking the C Stream
If you have fixes already for building it, perhaps merge those and then
remove it? That way, if we decided that we wanted to restore it (not that I
expect we would), we would be reverting to something that at least built
successfully.
Neal
On Mon, Jun 6, 2022 at 1:04 PM Micah Kornfield
wrote:
Would it make sense to make a draft PR with your branch so that folks can
comment on specific parts of it?
Neal
On Wed, Jun 1, 2022 at 10:20 AM Tobias Zagorni
wrote:
> Am Dienstag, dem 31.05.2022 um 12:41 -0700 schrieb Micah Kornfield:
> >
> > - Should we allow multiple runs of the same value f
+1 from me too to mark it as stable. De facto it is stable: there have been
no modifications to
https://github.com/apache/arrow/blob/master/cpp/src/arrow/c/abi.h since the
stream was added in 2020.
Neal
On Thu, May 26, 2022 at 12:32 PM Dewey Dunnington
wrote:
> I'm fairly new to this but have w
+1
On Tue, May 17, 2022 at 12:46 PM Andrew Lamb wrote:
> +1 (binding)
>
> On Mon, May 16, 2022 at 9:56 AM Andy Grove wrote:
>
> > I would like to propose that we move the Ballista project to a new
> > top-level *arrow-ballista* repository.
> >
> > The rationale for this (copied from the GitHub
ibs-only-l --static --silence-errors ${PKG_CONFIG_NAME}`"
> PKG_LIBS="$PKG_LIBS `PKG_CONFIG_PATH=${LIB_DIR}/pkgconfig pkg-config
> --libs-only-other --static --silence-errors ${PKG_CONFIG_NAME}`"
>
>
> Thanks,
> --
> kou
>
> In
> "Re: [R] Insta
old release candidates
> >
> > On Sat, May 7, 2022 at 3:40 AM Neal Richardson
> > wrote:
> >>
> >> I will handle the R submission to CRAN.
> >>
> >> Neal
> >>
> >> On Fri, May 6, 2022 at 6:14 PM Sutou Kouhei wrot
I will handle the R submission to CRAN.
Neal
On Fri, May 6, 2022 at 6:14 PM Sutou Kouhei wrote:
> > 9. [todo:kou?] upload RubyGems
>
> I'll do it once Homebrew and MSYS2 packages are updated.
>
> In
> "Re: [RESULT][VOTE] Release Apache Arrow 8.0.0 - RC3" on Fri, 6 May 2022
> 23:37:58 +0200,
Hmm, I see a couple of things:
* There are two errors at the end, one about pthread_cancel and one about
undefined symbols for snappy. I can't tell if the pthread issue is fatal.
* On the latter, I see that we're using snappy and lz4 from the system
(cmake finds them in the Arrow C++ build) but wh
1 - 100 of 830 matches
Mail list logo
