Le 31/10/2022 à 14:17, Neal Richardson a écrit :
The vote passes with 10 binding +1 votes and 9 other +1s. Thanks all.
The Infra policy change takes effect on November 6, so we have this week to
work through the migration and other questions.
It doesn't have to be done by November 6. Let's
The vote passes with 10 binding +1 votes and 9 other +1s. Thanks all.
The Infra policy change takes effect on November 6, so we have this week to
work through the migration and other questions. Let's discuss further on
https://github.com/apache/arrow/issues/14542 and its subtasks.
Neal
On Thu, O
+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:
> >
> > +1
> >
> > On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson <
> neal.p.richard...@gmail.com>
> > wrote:
> >
> > > I propose
+1
On Thu, 27 Oct 2022 at 07:27, Jacob Quinn wrote:
>
> +1
>
> On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson
> wrote:
>
> > 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 Ar
+1
On Thu, 27 Oct 2022 at 08:34, Matt Phelps wrote:
> +1
>
> From: Uwe L. Korn
> Date: Thursday, October 27, 2022 at 10:22 AM
> To: dev@arrow.apache.org
> Subject: Re: [VOTE] Move issue tracking to GitHub Issues
> CAUTION: This email originated from outside of the organiz
+1
From: Uwe L. Korn
Date: Thursday, October 27, 2022 at 10:22 AM
To: dev@arrow.apache.org
Subject: Re: [VOTE] Move issue tracking to GitHub Issues
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know
+1
On Thu, Oct 27, 2022, at 5:13 PM, Nic wrote:
> +1
>
> On Thu, 27 Oct 2022 at 14:00, Alenka Frim
> wrote:
>
>> +1
>>
>> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali
>> wrote:
>>
>> > +1
>> >
>> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington
>> > wrote:
>> >
>> > > +1 (non-binding)!
>>
+1
On Thu, 27 Oct 2022 at 14:00, Alenka Frim
wrote:
> +1
>
> On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali
> wrote:
>
> > +1
> >
> > On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington
> > wrote:
> >
> > > +1 (non-binding)!
> > >
> > > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson
> > > wrote:
>
+1
On Thu, Oct 27, 2022 at 2:36 PM prem sagar gali
wrote:
> +1
>
> On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington
> wrote:
>
> > +1 (non-binding)!
> >
> > On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson
> > wrote:
> >
> > > +1
> > >
> > > On 2022/10/26 23:02:33 Neal Richardson wrote:
> > > > I p
+1
On Thu, Oct 27, 2022 at 7:13 AM Dewey Dunnington
wrote:
> +1 (non-binding)!
>
> On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson
> wrote:
>
> > +1
> >
> > On 2022/10/26 23:02:33 Neal Richardson wrote:
> > > I propose that we move issue tracking from the ASF's Jira to GitHub
> > Issues.
> > > This
+1 (non-binding)!
On Thu, Oct 27, 2022 at 8:54 AM Eric Hanson wrote:
> +1
>
> On 2022/10/26 23:02:33 Neal Richardson wrote:
> > 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 o
+1
On 2022/10/26 23:02:33 Neal Richardson wrote:
> 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 `a
+1 (non-binding)
Rok
On Thu, Oct 27, 2022 at 9:19 AM Antoine Pitrou wrote:
>
> +1 (binding) but let's make sure we have a quality migration to keep as
> much of the JIRA metadata as possible.
>
> Regards
>
> Antoine.
>
>
> Le 27/10/2022 à 01:02, Neal Richardson a écrit :
> > I propose that we m
+1 (binding) but let's make sure we have a quality migration to keep as
much of the JIRA metadata as possible.
Regards
Antoine.
Le 27/10/2022 à 01:02, Neal Richardson a écrit :
I propose that we move issue tracking from the ASF's Jira to GitHub Issues.
This has been discussed on [1] and [
+1
On Wed, Oct 26, 2022 at 5:04 PM Neal Richardson
wrote:
> 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
> trac
+1, I'm very glad to see what will hopefully be a _slightly smoother_
experience for new contributors + issue reporters
-Jon
On Wed, Oct 26, 2022 at 7:05 PM David Li wrote:
> +1
>
> On Wed, Oct 26, 2022, at 20:01, Andy Grove wrote:
> > +1
> >
> > On Wed, Oct 26, 2022 at 5:50 PM L. C. Hsieh wr
+1
On Wed, Oct 26, 2022, at 20:01, Andy Grove wrote:
> +1
>
> On Wed, Oct 26, 2022 at 5:50 PM L. C. Hsieh wrote:
>
>> +1
>>
>>
>>
>> On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies
>> wrote:
>> >
>> > +1
>> >
>> > On 27/10/2022 12:02, Neal Richardson wrote:
>> > > I propose that we move is
+1
On Wed, Oct 26, 2022 at 5:50 PM L. C. Hsieh wrote:
> +1
>
>
>
> On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies
> wrote:
> >
> > +1
> >
> > On 27/10/2022 12:02, Neal Richardson wrote:
> > > I propose that we move issue tracking from the ASF's Jira to GitHub
> Issues.
> > > This has bee
+1
On Wed, Oct 26, 2022 at 4:08 PM Raphael Taylor-Davies
wrote:
>
> +1
>
> On 27/10/2022 12:02, Neal Richardson wrote:
> > 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 Arro
+1
On 27/10/2022 12:02, Neal Richardson wrote:
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/ar
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
21 matches
Mail list logo
