Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-14 Thread Wes McKinney
12, 2019 11:46:18 PM > To: dev > Subject: Re: [DISCUSS] Understanding Arrow's CI problems and needs > > I've started a new section to discuss proposals and current initiatives. I > know some of us have been working on some things but without much > coordination so far. It would b

Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-13 Thread Renjie Liu
Do we have ticket to track this? ?? Outlook for Android<https://aka.ms/ghei36> From: Andy Grove Sent: Saturday, October 12, 2019 11:46:18 PM To: dev Subject: Re: [DISCUSS] Understanding Arrow's CI problems and needs I've started a new se

Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-12 Thread Andy Grove
I've started a new section to discuss proposals and current initiatives. I know some of us have been working on some things but without much coordination so far. It would be good to track these efforts so everyone can comment on them. On Fri, Oct 11, 2019 at 11:11 AM Wes McKinney wrote: > It see

Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-11 Thread Wes McKinney
It seems some time has passed here. Would some others like to read the document and comment? This is important stuff. On Wed, Oct 2, 2019 at 2:20 PM Krisztián Szűcs wrote: > > The current document greatly summarizes the current situation, but in > order to properly compare and eventually select a

Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-02 Thread Krisztián Szűcs
The current document greatly summarizes the current situation, but in order to properly compare and eventually select a solution we need a a detailed list of explicit features with some sort of classification, like should/must have. For example our future CI system must support "PRs from forks". Af

Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-02 Thread Wes McKinney
I reviewed the document, thanks for putting it together! I think it captures most of the requirements and the challenges that we are currently facing. I think that anyone who is actively contributing to the project or merging pull requests should read this document since this affects all of us. On

Re: [DISCUSS] Understanding Arrow's CI problems and needs

2019-10-01 Thread Wes McKinney
Thanks Neal for starting this discussion. I will review and comment. I will say that as a maintainer the current situation is very nearly intolerable. As by far and away the most prolific merger-of-PRs [1], I've been negatively affected by the long queueing times and delayed feedback cycles. The p

[DISCUSS] Understanding Arrow's CI problems and needs

2019-10-01 Thread Neal Richardson
Hi all, Over the last few months, I've seen a lot of frustration and discussion around the shortcomings of our current CI. I'm also seeing debate over a few possible solutions; unfortunately, the debates tend not to resolve in a clear, decisive way, and we end up having the same debates repeatedly.