Attendees: - Ian Cook - Will Jones - David Li - Rok Mihevc - Dragoș Moldovan-Grünfeld - Aldrin Montana - Matthew Topol - Jacob Wujciak
Discussion: Book about Apache Arrow released this week - Matt Topol's book "In-Memory Analytics with Apache Arrow" goes on sale this Friday June 24 [1] Conference about Apache Arrow happening this week - This Thursday June 23, Voltron Data is hosting "The Data Thread", a virtual conference focused on the Apache Arrow ecosystem [2] Discussion about patch releases - Prompted by recent reports of a vulnerability in a dependency of the Arrow Go package [3] and a missing feature in one of the PyArrow wheels [4], there was an inconclusive discussion about our current process for creating patch releases for packages maintained the apache/arrow monorepo and whether this meets the needs of the different language libraries. - This led to a discussion about whether the Arrow maintainers should provide patch releases for older major versions of Arrow, which would fix critical bugs without introducing any breaking changes. It was agreed that this would likely be burdensome because of the unpredictable level of difficulty in backporting fixes and the predictably high level of difficulty in producing releases, verifying them, packaging them, and distributing them. Discussion about versioning conventions - There was an inconclusive discussion about whether we should consider moving away from the current Arrow release versioning conventions in which each quarterly release of the packages maintained in the apache/arrow monorepo increments the major version number. As some implementations of Arrow become more stable, it is unclear to some whether we should always be incrementing the major version number, which under the semantic versioning scheme indicates that the release includes breaking changes to the API. Always incrementing major version numbers creates some difficulty for package maintainers, for example for the Go package. - Note that the current semantic versioning convention was explained in the Arrow 1.0.0 release blog post [5] Upcoming 9.0.0 release targeted for mid-July - Please see the email about this upcoming release [6] - There have been some changes to the release process that will take effect with this release, as described on the mailing list [7] and in the updated release management guide [8]. There was another PR merged just today with some additional changes to the release management guide [9]. Please review the updated processes if you will be participating in the 9.0.0 release. - It is anticipated that fewer problems will be identified during the release verification process because of the increased visibility and attention on fixing nightly CI failures, for example using the Crossbow nightly report [10] [1] https://lists.apache.org/thread/gnlby6hs2jl4fhtk6wlx0zmw3ox3lqyj [2] https://thedatathread.com [3] https://lists.apache.org/thread/zyhl1r1nkp82lr6wtyz6h2z5knoly73q [4] https://issues.apache.org/jira/browse/ARROW-16779 [5] https://arrow.apache.org/blog/2020/07/24/1.0.0-release/ [6] https://lists.apache.org/thread/8b7yyzgmtb6mq7od0jbntvfflm0vv72o [7] https://lists.apache.org/thread/g6mqpyq2hc11xbgrq2pf653njzy53plt [8] https://arrow.apache.org/docs/dev/developers/release.html [9] https://github.com/apache/arrow/pull/13308 [10] https://crossbow.voltrondata.com On Wed, Jun 22, 2022 at 10:31 AM Ian Cook <i...@ursacomputing.com> wrote: > > Hi all, > > Our biweekly sync call is today at 12:00 noon Eastern time. > > 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
