+1 (binding)
In
"[VOTE] Split JS implementation and Release Process" on Wed, 7 May 2025
10:48:40 +0200,
Raúl Cumplido wrote:
> Hi,
>
> I would like to propose splitting the JS implementation and the
> corresponding release process to its own repository.
>
> Motivation:
>
> * We want to
Let me open a thread, its a valid suggestion, will attach the discussions
Thanks,
Susmit
On Wed, May 7, 2025 at 8:34 PM Julian Hyde wrote:
> This thread is getting rather long. I think you should open a case. That’s
> a permanent place that you can attach screenshots, stack traces. And it
> wil
+1 (binding)
I ran dev/release/verify_rc.sh 18.3.0 0 on MacOS 15.4 (M4)
On Wed, May 7, 2025 at 2:13 AM Saurabh Singh wrote:
> +1 (Non-binding)
>
> I ran the following on Ubuntu 24.10/amd64:
>
> dev/release/verify_rc.sh 18.3.0 0
>
> with:
>
> * go version go1.23.7 linux/amd64
>
> Thanks,
> S
+1
On Wed, May 7, 2025 at 8:38 AM Bryce Mecum wrote:
> +1 (binding)
>
> On Wed, May 7, 2025 at 1:48 AM Raúl Cumplido wrote:
> >
> > Hi,
> >
> > I would like to propose splitting the JS implementation and the
> > corresponding release process to its own repository.
> >
> > Motivation:
> >
> > *
A brief update on this from me - I've now added the Python, R, C++, and
Java cookbooks as a source for the kapa.ai question bot, so code examples
from those should be on there now.
At a later point, I'll take a look at potentially adding GitHub PRs and
issues, but I'd like to test what we have so
Would we be able to feed it the arrow-go documentation too?
On Wed, May 7, 2025, 12:52 PM Nic Crane wrote:
> A brief update on this from me - I've now added the Python, R, C++, and
> Java cookbooks as a source for the kapa.ai question bot, so code examples
> from those should be on there now.
>
+1 (binding)
On Wed, May 7, 2025 at 1:48 AM Raúl Cumplido wrote:
>
> Hi,
>
> I would like to propose splitting the JS implementation and the
> corresponding release process to its own repository.
>
> Motivation:
>
> * We want to reduce needless major releases to avoid unnecessary user
> burden.
>
This thread is getting rather long. I think you should open a case. That’s a
permanent place that you can attach screenshots, stack traces. And it will also
be found by anyone who has the same problem in future.
Julian
> On May 7, 2025, at 2:51 AM, David Li wrote:
>
> Thanks for reporting b
+1 (binding)
Am Mi., 7. Mai 2025 um 15:07 Uhr schrieb Neal Richardson
:
>
> +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 é
+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
> >>
+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
corresponding release process to its own repository.
Motivation:
* We want to reduce needless major releases to avoid unnecessary user
burden.
* We want to avoid
+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
>> corresponding release process to its own repository.
>>
>> Motivation:
>>
>> * We
Thanks for reporting back. (Note, the attachment didn't make it.) Hmm, I'd
probably need to poke at it in a debugger. But it sounds like the callbacks are
getting lost somehow. (I'm not a fan of how the Java API tries to adapt an
async API into a synchronous one, not least because it leads to we
Hi,
I would like to propose splitting the JS implementation and the
corresponding release process to its own repository.
Motivation:
* We want to reduce needless major releases to avoid unnecessary user
burden.
* We want to avoid needless release tasks when releasing apache/arrow if it
is not ne
+1 (Non-binding)
I ran the following on Ubuntu 24.10/amd64:
dev/release/verify_rc.sh 18.3.0 0
with:
* go version go1.23.7 linux/amd64
Thanks,
Saurabh
On Wed, 7 May 2025 at 05:30, Sutou Kouhei wrote:
> +1 (binding)
>
> I ran the following on Debian GNU/Linux sid:
>
> dev/release/verify
15 matches
Mail list logo
