+1. If there is demand for an Asia-friendly time we can change things up from
week to week.
> On Aug 16, 2016, at 10:52 AM, Jacques Nadeau wrote:
>
> sounds good
>
>> On Tue, Aug 16, 2016 at 10:39 AM, Julien Le Dem wrote:
>>
>> Based on the feedback I'm proposing Thursday Aug 18 at 4PM UTC
sounds good
On Tue, Aug 16, 2016 at 10:39 AM, Julien Le Dem wrote:
> Based on the feedback I'm proposing Thursday Aug 18 at 4PM UTC as the first
> Arrow sync.
> That's:
> - 9AM PDT (San Francisco)
> - 12PM EDT (New York)
> - 5PM CET (London)
> - 6PM CEST (Paris, Berlin)
>
> On Tue, Aug 9, 2016 a
Based on the feedback I'm proposing Thursday Aug 18 at 4PM UTC as the first
Arrow sync.
That's:
- 9AM PDT (San Francisco)
- 12PM EDT (New York)
- 5PM CET (London)
- 6PM CEST (Paris, Berlin)
On Tue, Aug 9, 2016 at 6:45 AM, Uwe L. Korn wrote:
> +1 for bi-weekly and europeen friendly times: CET (GM
See ARROW-262
On Mon, Aug 15, 2016 at 3:38 PM, Wes McKinney wrote:
> These IPC details we should definitely document outside of the code.
>
> For the String/Binary type question, I want to start a document that
> explains the logical data types in Message.fbs in terms of
>
> - what Arrow memory
