Hi Neal, Are you the release manager for 2.0? I've been working on the task to disable server verification in Flight clients, and it appears we'll need to update the minimum gRPC version to at least 1.27 to support this.
Would it be OK to do this for the 2.0. release? It looks like we also need to update Ursa configurations here: https://github.com/ursa-labs/ursabot/blob/e958c5f95b31e98108df54cf13596c4fde944c3a/projects/arrow/docker/conda-cpp.txt#L19 The relevant JIRA is: https://issues.apache.org/jira/browse/ARROW-10105 The Java version of this improvement has already been merged to master. On Mon, Oct 5, 2020 at 6:41 PM Neal Richardson <neal.p.richard...@gmail.com> wrote: > Hi folks, checking back in here. Thanks to our collective effort, we're > making good progress towards the 2.0 release, but there's still a bit more > to do. Per > https://cwiki.apache.org/confluence/display/ARROW/Arrow+2.0.0+Release, > we're at 31 unstarted and another 31 in-progress issues left for 2.0. > Blockers are down to 1, which I believe has a pull request up, but there > are still a few nightly builds failing (JIRAs ARROW-10175 to -10178). > > We are planning to cut a release candidate on Friday, less than 4 days from > now, so please be working to wrap up any issues you have in flight, and > bump issues to 3.0 that you aren't going to be able to get to in time. > > Neal > > On Tue, Sep 29, 2020 at 5:46 PM Neal Richardson < > neal.p.richard...@gmail.com> > wrote: > > > Thanks Neville. I also just bumped 60 C++/Python issues (new features, > > unassigned, not created recently) from 2.0. We're at 122 now, which still > > needs some pruning. I think something that more folks can do is review > the > > issues assigned to them and make sure that they're planning to get all of > > those done for 2.0, otherwise bump to 3.0 or unassign themselves (or > both). > > > > Neal > > > > On Tue, Sep 29, 2020 at 5:01 PM Neville Dipale <nevilled...@gmail.com> > > wrote: > > > >> Hi Neal, > >> > >> I've pruned the Rust backlog a bit, but only changed PRs that I've > either > >> opened, > >> or those that I presume nobody is currently working on. > >> > >> There's 2 major features I've been working on: > >> > >> 1. Writing Arrow data to Parquet (separate branch) > >> 2. Integration testing > >> > >> I'll prioritise 2 as that's on the main branch, and we're nearly there. > >> However, with the arrow parquet writer, I'd like to ask the Rust > >> developers > >> if > >> we will want to release the WIP support with 2.0.0, or if we hold back > and > >> keep > >> chipping away from a separate branch. > >> > >> There's been a new contributor who's offered to help with the writer, > >> so I think I'll be able to make more progress with her. > >> > >> Neville > >> > >> On Wed, 30 Sep 2020 at 00:34, Neal Richardson < > >> neal.p.richard...@gmail.com> > >> wrote: > >> > >> > Hi folks, > >> > As has been discussed in the biweekly meetings (and in the notes from > >> those > >> > meetings here on the mailing list), we're looking at an October > timeline > >> > for our next release since we are going about 3 months between > >> releases. So > >> > that we might get the release voted on and shipped by the middle of > the > >> > month, we should aim to be ready to cut our first (and final!) release > >> > candidate by next Friday, October 9. > >> > > >> > According to > >> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+2.0.0+Release > , > >> > there are still 178 issues tagged for 2.0 that are not yet started. > That > >> > seems... ambitious. Please do go through the backlog and push to the > >> next > >> > release (i.e. 3.0.0) unassigned issues that aren't likely to land in > the > >> > next 10 days. > >> > > >> > Likewise, I see that there are a few issues tagged as "blocker". Let's > >> > determine whether those truly should prevent a release candidate from > >> being > >> > made, and if so, let's make sure they get done ASAP. > >> > > >> > Neal > >> > > >> > > > -- *James Duong* Lead Software Developer Bit Quill Technologies Inc. Direct: +1.604.562.6082 | jam...@bitquilltech.com https://www.bitquilltech.com This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.
