[DISCUSS] 3.1.0 release

Hi Folks, It's been a while since we last released a minor version of Impala. 3.0.0 is out since May, and since then a couple of pretty cool features and a good number of improvements are checked in. I propose that we release 3.1.0 soon and I volunteer to be its release manager. Please speak up a

Re: [DISCUSS] 3.1.0 release

+1 I know that I and some other people have been pushing to burn down the critical bugs remaining targeted for 3.1 and push out less critical work to 3.2 so we will be in a good position to do a release (it's been a while since 3.0!). I have this filter to track the open JIRAs targeted for 3.1: ht

Re: [DISCUSS] 3.1.0 release

+1. Thanks for volunteering, Zoltan! Do you concur with Tim about leaving out some big recent changes, assuming authors request so? On Mon, Nov 5, 2018 at 9:10 AM Tim Armstrong wrote: > +1 > > I know that I and some other people have been pushing to burn down the > critical bugs remaining target

Re: [DISCUSS] 3.1.0 release

+1. I concur with Tim that it's safer to leave out this commit for IMPALA-7213 for 3.1 to give it more bake time. Thanks, Michael On Mon, Nov 5, 2018 at 9:32 AM Jim Apple wrote: > +1. Thanks for volunteering, Zol

Re: [DISCUSS] 3.1.0 release

Hi Zoltan, When you said, "I propose that we release 3.1.0 soon", how "soon" do you have in mind? I have a few doc tickets for the new features, 3 in reviews, and 3 to start, including the Timezone changes. alex r On Mon, Nov 5, 2018 at 6:50 AM, Zoltan Borok-Nagy wrote: > Hi Folks, > > It's b

Re: [DISCUSS] 3.1.0 release

Thanks for the replies. Yeah, it seems reasonable to leave out the risky changes. I just have a technical question about it. Should we a) select an early branching point then do a lot of cherry picks for the commits we want in and leave out the risky ones b) select a recent branching point then rev

Re: [DISCUSS] 3.1.0 release

Hey Zoli! Just a quick comment about the technical part: Isn't it possible to do an interactive git rebase (-i option) and then you can mark the unwanted commits as 'drop' in the commit list. Cheers, Gabor On Tue, Nov 6, 2018 at 3:11 PM Zoltan Borok-Nagy wrote: > Thanks for the replies. Yeah,

Re: [DISCUSS] 3.1.0 release

> > I just have a technical question about it. Should we > a) select an early branching point then do a lot of cherry picks for the > commits we want in and leave out the risky ones > b) select a recent branching point then revert the risky commits on the > release branch > I think (a) is easier f

Re: [DISCUSS] 3.1.0 release

Thanks for the suggestions. I wasn't aware of interactive git rebase. It might makes it simpler to carry out (a) if there are no conflicts. Zoltan On Tue, Nov 6, 2018 at 4:06 PM Jim Apple wrote: > > > > I just have a technical question about it. Should we > > a) select an early branching point

Re: [DISCUSS] 3.1.0 release

Hey Folks, It's been a week since we last talked about the 3.1.0 release. So I guess we'll only leave out the RPC-related commit from Michael. Is it OK if I start the branching and testing tomorrow? Then, I'll cherry-pick the docs-related changes from Alex after they land in the repo. Or, do yo

Re: [DISCUSS] 3.1.0 release

I'd say go for it! Thanks! On Mon, Nov 12, 2018 at 9:17 AM Zoltan Borok-Nagy wrote: > Hey Folks, > > It's been a week since we last talked about the 3.1.0 release. > > So I guess we'll only leave out the RPC-related commit from Michael. > > Is it OK if I start the branching and testing tomorr

Re: [DISCUSS] 3.1.0 release

I think either way is fine. On Mon, Nov 12, 2018 at 9:17 AM Zoltan Borok-Nagy wrote: > Hey Folks, > > It's been a week since we last talked about the 3.1.0 release. > > So I guess we'll only leave out the RPC-related commit from Michael. > > Is it OK if I start the branching and testing tomorrow

Re: [DISCUSS] 3.1.0 release

I think about 7 working days will be enough to wrap up the doc work for 3.1: - TOPN query option - SHUTDOWN command - TIMEZONE changes - Minor release-related work On Mon, Nov 12, 2018 at 9:17 AM, Zoltan Borok-Nagy wrote: > Hey Folks, > > It's been a week since we last talked about the 3.1.0 r

Re: [DISCUSS] 3.1.0 release

Hey Folks, Status of the 3.1.0 release: I chose IMPALA-5950 (e3a7027) as branching point, and cherry picked commits until IMPALA-5031 (067657a) (inclusive range) with the following exceptions: - IMPALA-7213 : Port ReportExecStatus() RPCs t

Re: [DISCUSS] 3.1.0 release

Hi Zoltan, As you may have noticed, the test addressed in IMPALA-7148 was marked as 'xfail' before the fix of IMPALA-4063 so cherry-picking IMPALA-7148 should have no material effect to that test without IMPALA-4063. Thanks, Michael On Mon, Nov 19, 2018 at 8:28 AM Zoltan Borok-Nagy wrote: > He

Re: [DISCUSS] 3.1.0 release

I count 10 doc commits since your last cherry-pick: [image: image.png] Thanks! On Mon, Nov 19, 2018 at 8:28 AM Zoltan Borok-Nagy wrote: > Hey Folks, > > Status of the 3.1.0 release: > > I chose IMPALA-5950 (e3a7027) as branching point, and cherry picked commits > until IMPALA-5031 (067657a) (in

Re: [DISCUSS] 3.1.0 release

Hi, Michael: Thanks, I missed that. I reverted IMPALA-7148 since it is targeted for 3.2.0 and doesn't have any effect without IMPALA-4063. Alexandra: Unfortunately I cannot see the image you attached. Anyway, I also counted 10 new doc commits targeted for 3.1.0: https://git-wip-us.apache.org/repo