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 > > >
