Sorry to all who will have missed the call because of the Daylight
Saving Time change. Here are the notes:

Attendees:
James Duong, Micah Kornfield, Eduardo Ponce, Will Jones, Rok Mihevc,
David Li, Niranda Perera, Alenka Frim, Ian Joiner

Discussion:
* James Duong - Out of curiosity - does Arrow have nightly builds. It
does: [1], [2], perhaps more
* David Li - We want to do a FlightSQL change vote soon. Please take a
look at the PR. Update will come to the ML as well. ([3], [4]).
Reviewers for the JDBC PR also welcome [5].
* Micah Kornfeld - Inlined data for Flight PR: [6]. Please review.
Micah might introduce another minor change still but other than that
it's pretty complete.
* James Duong - Do we do JDK 8 testing where we build on JDK 11 and
test on JDK 8? We currently don't. We would need another CI process.
We might not want to invest into JDK 8 since it's EOL this month. We
would like a JDK support policy and Micah will start a ML thread.
Perhaps a cross-version build-test set is in order. E.g.: build on
version x and test on versions y through z. Cycle x through supported
versions.

[1] https://github.com/ursacomputing/crossbow/releases
[2] 
https://arrow.apache.org/docs/python/install.html#installing-nightly-packages
[3] https://github.com/apache/arrow/pull/11982
[4] https://github.com/apache/arrow/pull/11999
[5] https://github.com/apache/arrow/pull/12254
[6] https://github.com/apache/arrow/pull/12571

On Wed, Mar 16, 2022 at 2:19 PM Ian Cook <i...@ursacomputing.com> wrote:
>
> Hi all,
>
> Our biweekly sync call is today at 12:00 noon Eastern time. For
> attendees in locations where Daylight Saving Time is observed but has
> not yet begun, please note that this is one hour earlier than the
> usual time in your local time zone.
>
> The Zoom meeting URL for this and other biweekly Arrow sync calls is:
> https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09
>
> Alternatively, enter this information into the Zoom website or app to
> join the call:
> Meeting ID: 876 4903 3008
> Passcode: 958092
>
> Thanks,
> Ian

Reply via email to