Re: 4.0 release preparation

Thanks for your feedback last night all of which has been addressed! I will address all comments at least daily so that the ORC writer can be included without blocking the release! Ying > On Apr 13, 2021, at 9:07 PM, Micah Kornfield wrote: > > I'll try to take a look tonight but it might be

Re: 4.0 release preparation

I'll try to take a look tonight but it might be tight if there is substantial feedback. On Tue, Apr 13, 2021 at 5:29 PM Wes McKinney wrote: > I agree it would be good to get the ORC writer in this release. > > On Tue, Apr 13, 2021 at 7:20 PM Ying Zhou wrote: > > > > What about this one? You

Re: 4.0 release preparation

I agree it would be good to get the ORC writer in this release. On Tue, Apr 13, 2021 at 7:20 PM Ying Zhou wrote: > > What about this one? You know, the C++/Python ORC writer. > https://github.com/apache/arrow/pull/8648 > > > Ying > > On Apr 13, 2021,

Re: 4.0 release preparation

What about this one? You know, the C++/Python ORC writer. https://github.com/apache/arrow/pull/8648 Ying > On Apr 13, 2021, at 12:52 PM, Neal Richardson > wrote: > > I think we're getting close to closing out 4.0. Let's give until the end of >

Re: 4.0 release preparation

I think we're getting close to closing out 4.0. Let's give until the end of Wednesday to get any outstanding pull requests reviewed and merged, and Krisztián will plan to cut a release candidate on Thursday. If there are any objections, please speak up! Neal On Sun, Apr 11, 2021 at 9:15 AM

Re: 4.0 release preparation

Le 10/04/2021 à 23:06, Weston Pace a écrit : Nightly build triage (based on nightly builds from 4/9): Failed Tasks: - conda-linux-gcc-py36-aarch64: ARROW-12324 (conda builds timing out, conda slow) - conda-linux-gcc-py37-aarch64: ARROW-12324 (conda builds timing out, conda slow) -

Re: 4.0 release preparation

gt; Neal > > > > > > On Fri, Apr 9, 2021 at 12:33 AM Sutou Kouhei > wrote: > > > > > > > Hi, > > > > > > > > One more concern: > > > > > > > > * ASF's Bintray -> Artifactory migration isn't finished yet. &

Re: 4.0 release preparation

gt; Neal > > > > On Fri, Apr 9, 2021 at 12:33 AM Sutou Kouhei wrote: > > > > > Hi, > > > > > > One more concern: > > > > > > * ASF's Bintray -> Artifactory migration isn't finished yet. > > > > > > > https://lists.apache.org/thread.html/r9200fed3fa812f8c7de07a2500425

Re: 4.0 release preparation

tifactory migration isn't finished yet. > > > > https://lists.apache.org/thread.html/r9200fed3fa812f8c7de07a2500425f258db3231baa8e05f288175e4a%40%3Cbuilds.apache.org%3E > > > > I think that this is not a blocker. We'll not release > > deb/rpm packages when we release 4.0. We can release > > deb/r

Re: 4.0 release preparation

t release > deb/rpm packages when we release 4.0. We can release > deb/rpm packages later. > > > Thanks, > -- > kou > > > In > "4.0 release preparation" on Mon, 5 Apr 2021 19:39:30 -0700, > Neal Richardson wrote: > > > Hi all, > >

Re: 4.0 release preparation

we release 4.0. We can release deb/rpm packages later. Thanks, -- kou In "4.0 release preparation" on Mon, 5 Apr 2021 19:39:30 -0700, Neal Richardson wrote: > Hi all, > It's release time again. By our quarterly release pace, we are scheduled > for an April 4.0.0 release. G

Re: 4.0 release preparation

NVM, I'm dumb. I was looking at the blocking issues on my phone and didn't scroll enough. Carry on. On Tue, Apr 6, 2021 at 8:50 AM Eric Burden wrote: > Where's the wiki page? I looked over the 6 blocking issues, and they seem > a bit beyond my scope at the moment. I'd like to review the 157 to

Re: 4.0 release preparation

Where's the wiki page? I looked over the 6 blocking issues, and they seem a bit beyond my scope at the moment. I'd like to review the 157 to see if there's anything I can tackle. On Mon, Apr 5, 2021 at 9:39 PM Neal Richardson wrote: > Hi all, > It's release time again. By our quarterly release

4.0 release preparation

Hi all, It's release time again. By our quarterly release pace, we are scheduled for an April 4.0.0 release. Given the time it takes to prepare and approve a release, I think we should aim to close out our release scope by the end of this week, beginning of next at latest, so that we can ensure a