Hi,
It seems that we can enable GitHub Discussions by .asf.yaml:
https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#repository-features
Do we want to enable GitHub Discussions for apache/arrow?
We can use GitHub Discussions for user support like
u...@arrow.apache.org.
See also
Hi,
This is a similar discussion to the "[DISCUSS] Split Go
release process" thread[1], the "[DISCUSS] Split Java
release process" thread[2] and the "[DISCUSS] Split R release
process" thread[3]:
[1] https://lists.apache.org/thread/fstyfvzczntt9mpnd4f0b39lzb8cxlyf
[2] https://lists.apache.org/thr
That makes sense to me. 500MB is a bit excessive (well, 94MB also sounds
excessive but I suppose that's LLVM).
Maybe we can host the separated debug symbols as part of the GitHub release
instead?
re: runner space, something like this should work [1].
[1]:
https://github.com/apache/arrow-adbc/
Hi all,
Just wanted to say I appreciate the meeting notes also as I am mostly
unable to attend.
Best, Alenka
V sre., 12. mar. 2025, 18:11 je oseba Raúl Cumplido
napisala:
> Hi,
>
> I am also unable to make it lately but I follow the meeting notes.
> Thanks for taking those.
>
> Regards,
> Raúl
Hi,
I would like to propose the following release candidate (RC1) of
Apache Arrow Go version 18.2.0.
This release candidate is based on commit:
166cf7b1fe12dd207a51125e6fc4e75edd7dfaf0 [1]
The source release rc1 is hosted at [2].
Please download, verify checksums and signatures, run the unit te
+1 (binding)
I ran `dev/release/verify_rc.sh 18.2.0 1` on macOS 15 (aarch64).
On Wed, Mar 12, 2025 at 11:07 AM Matt Topol wrote:
>
> Hi,
>
> I would like to propose the following release candidate (RC1) of
> Apache Arrow Go version 18.2.0.
>
> This release candidate is based on commit:
> 166cf7b
Thank you -- that is super helpful
On Wed, Mar 12, 2025 at 1:51 PM Jacob Wujciak wrote:
> +1
>
> Just a quick note, there is no need for an INFRA ticket, as a PMC you
> can self-serve the repo creation in boxer [1].
>
> Any repo secrets you might need can be set via the gh cli tool and
> also do
+1 but my opinion doesn't matter :D
signature.asc
Description: OpenPGP digital signature
+1
On Wed, Mar 12, 2025 at 1:31 PM Andrew Lamb wrote:
> Hello,
>
> I would like to call a lazy consensus vote to move the code for
> object_store into its own repository, mostly for clarity and release
> management convenience
>
> We have discussed this previously [1].
>
> Unless there are objec
+1
Just a quick note, there is no need for an INFRA ticket, as a PMC you
can self-serve the repo creation in boxer [1].
Any repo secrets you might need can be set via the gh cli tool and
also don't require an INFRA ticket anymore. INFRA only asks that you
use an ARROW_ prefix for secrets. Thanks
Hello,
I would like to call a lazy consensus vote to move the code for
object_store into its own repository, mostly for clarity and release
management convenience
We have discussed this previously [1].
Unless there are objections I will plan to file an infrastructure ticket in
a week and begin t
After talking with Bryce, I'm gonna fix the encryption tests according to
the update he mentioned [1] and then cut a new RC. It's good to ensure all
the tests work correctly against the up-to-date versions of the
parquet-testing files.
Hopefully it's not too inconvenient to ask for everyone to ple
+0
I ran dev/release/verify_rc.sh 18.2.0 on macOS aarch64 and got
failures in the Parquet encryption suite [1].
It looks like it's because the encryption test files in
parquet-testing were updated in [2]. arrow-go is pinned to an earlier
version of parquet-testing, its tests pass against that ver
Hello all,
I'd like to propose a feature freeze date of Tuesday, April 1th, 2025
for the upcoming 20.0.0 release of Arrow. Please take a look through
the milestone [1] to ensure it includes the issues you expect and to
see if any need your attention. There are currently no open issues labeled
as b
Hi,
I am also unable to make it lately but I follow the meeting notes.
Thanks for taking those.
Regards,
Raúl
El mié, 12 mar 2025 a las 18:07, Jean-Baptiste Onofré ()
escribió:
> Hi folks,
>
> sorry, I missed the meeting, I will attend the next one.
>
> Regards
> JB
>
> On Wed, Mar 12, 2025 at
Hi
Yes, agree with Kou and Jacob: we should probably strip and "square"
to only keep debug.
Thoughts ?
Regards
JB
On Wed, Mar 12, 2025 at 12:41 PM Jacob Wujciak wrote:
>
> Thanks for testing this Logan! We probably have to clear some more
> disk space on the runner, this is a problem we have h
Hi folks,
sorry, I missed the meeting, I will attend the next one.
Regards
JB
On Wed, Mar 12, 2025 at 4:08 AM Ian Cook wrote:
>
> Our next biweekly Arrow community meeting is this Wednesday 12 March 16:00
> UTC / 12:00 EDT / 9:00 PDT.
>
> *** For attendees in countries that have not yet switche
Hello Ian,
Thanks for the notice. Unfortunately, I'll miss today's Arrow community
meeting due to an urgent matter.
Regards,
Saurabh
On Wed, 12 Mar 2025 at 08:38, Ian Cook wrote:
> Our next biweekly Arrow community meeting is this Wednesday 12 March 16:00
> UTC / 12:00 EDT / 9:00 PDT.
>
> ***
Thanks for testing this Logan! We probably have to clear some more
disk space on the runner, this is a problem we have had before, they
keep adding things to the image.
A 5x increase seems a bit much to integrate into the normal builds, so
Kou's approach is probably best?
Am Mi., 12. März 2025 um
19 matches
Mail list logo
