Arrow sync call February 17 at 12:00 US/Eastern, 17:00 UTC

[Neal Richardson <ne...@gmail.com>]

Hi all,
Reminder that our biweekly call is coming up at
https://meet.google.com/vtm-teks-phx. All are welcome to join. Notes will
be shared with the mailing list afterward.

Neal

Re: Arrow sync call February 17 at 12:00 US/Eastern, 17:00 UTC

[Neal Richardson <ne...@gmail.com>]

Apologies for the delay in sending the notes out.

Attendees:

Ian Cook
Andy Grove
Jonathan Keane
Micah Kornfield
Hoi Link Tiffany Lam
Andrew Lamb
Jorge Cardoso Leitão
Kirill Lykov
Rok Mihevc
Weston Pace
Ruan Pearce-Authers
Neal Richardson
Naman Udasi
Dmitry Unknown

Discussion:

* PR/JIRA tool: Andrew Lamb is pursuing this, clarifying what ASF
requirements/constraints there are (see mailing list discussion)
* Maintenance releases: we discussed options for making it easier to do
bugfix releases between our quarterly major releases. I will send a formal
proposal to the mailing list with what we discussed
* Flight SQL: discuss breaking down into smaller components to move forward

On Wed, Feb 17, 2021 at 4:55 AM Antoine Pitrou <an...@python.org> wrote:

>
> Le 17/02/2021 à 12:07, Andrew Lamb a écrit :
> > *Proposal*:  Allow Rust and other implementations release additional
> point
> > / maintenance  versions at a different cadences, out of lockstep with the
> > major arrow releases. We could still release the Rust library as part of
> > the major Arrow releases, but we would release both bug fix / patch
> > versions as well as intermediate feature releases of our various crates
>
> No opposition from me.
>
> Best regards
>
> Antoine.
>

Re: Arrow sync call February 17 at 12:00 US/Eastern, 17:00 UTC

[Antoine Pitrou <an...@python.org>]

Le 17/02/2021 à 12:07, Andrew Lamb a écrit :
> *Proposal*:  Allow Rust and other implementations release additional point
> / maintenance  versions at a different cadences, out of lockstep with the
> major arrow releases. We could still release the Rust library as part of
> the major Arrow releases, but we would release both bug fix / patch
> versions as well as intermediate feature releases of our various crates

No opposition from me.

Best regards

Antoine.

Re: Arrow sync call February 17 at 12:00 US/Eastern, 17:00 UTC

[Andrew Lamb <al...@influxdata.com>]

I have two items I would like to propose for the agenda if there is time:

1. Manual creation of JIRA Tickets
*Background/Issue*: Currently all contributors are required to make a JIRA
account and do some mechanical JIRA creation to create well formed Arrow
PRs. This is mindless work and people who are used to it may forget the
barrier it imposes on casual contributions and burden on maintainers to
keep JIRA synced.
*Proposal*: Write a bot / script that uses the title of new PRs to open the
appropriate JIRA / components. Devs / maintainers would only have to ensure
the title of PRs started with the correct components.

2. Slow Release Process + Dearth  of Maintenance Releases
*Background / Issues: I*nfrequent releases (every three months), and lack
of maintenance patchsets mean that many users of the Rust Arrow crate need
to pull in some version of the `master` branch as that is the only way they
can get bug fixes in the intervening three months between releases-- this
causes friction with users, and pressure to keep APIs more compatible than
befit a project at the Rust Implementation's stage of maturity.
*Proposal*:  Allow Rust and other implementations release additional point
/ maintenance  versions at a different cadences, out of lockstep with the
major arrow releases. We could still release the Rust library as part of
the major Arrow releases, but we would release both bug fix / patch
versions as well as intermediate feature releases of our various crates

On Tue, Feb 16, 2021 at 10:53 PM Neal Richardson <
neal.p.richardson@gmail.com> wrote:

> Hi all,
> Reminder that our biweekly call is coming up at
> https://meet.google.com/vtm-teks-phx. All are welcome to join. Notes will
> be shared with the mailing list afterward.
>
> Neal
>