Re: [DISCUSS] 3.2.0 release

Sure, I see you point as we have already discussed on the "Impala Dev Community Meeting" on Monday. Since then turned out for me that Alex has a similar release notes doc described here up her sleeve that we could use. Alex could you please share once you have a public version of it? Gabor On

Re: [DISCUSS] 3.2.0 release

Hey, I agree with Quanlong. It's increasingly difficult for me to keep up with what's new, having a short version of the release notes with a summary for each item (about the intent and impact, if not trivial from the jira summary) would be useful. For example, KRPC was turned on by default in

Re: [DISCUSS] 3.2.0 release

Hi Gabor, IMO, the change log is too detailed to be readable for users. There're no any highlights. It's hard for users to find significant changes. A summarized doc about new features and significant bug fixes (not any fixes for tests) will be more useful for them. Something like these: -

Re: [DISCUSS] 3.2.0 release

It wasn't late, no problem. I added it to the release alongside with the doc changes from Alex. I consider now the release content final and I move on with the next steps of the release creation. Cheers, Gabor On Fri, Mar 15, 2019 at 8:18 PM Thomas Tauber-Marshall < tmarsh...@cloudera.com>

Re: [DISCUSS] 3.2.0 release

If its not too late, it would be great to include this fix: https://issues.apache.org/jira/browse/IMPALA-8299 On Thu, Mar 14, 2019 at 5:38 AM Gabor Kaszab wrote: > (Sorry, accidentally sent out the mail too early) > - Alex sent in a number of doc commits covering changes that are already > in,

Re: [DISCUSS] 3.2.0 release

(Sorry, accidentally sent out the mail too early) - Alex sent in a number of doc commits covering changes that are already in, so I'll include them as well: - 76286bf2c0320cce0eb1bf0c269d344255b4dd0e IMPALA-7974 - 9cc75c59d5a09bd898bdf05cc64a98a70ffd IMPALA-8133 -

Re: [DISCUSS] 3.2.0 release

Hey, Just for the record I gather the requests and conclusions here in one mail: - It's fine to cut at 9686545bfd7236350d165813621bf783b42d1c18 IMPALA-6503: Support reading complex types from ORC (inclusive) - As

Re: [DISCUSS] 3.2.0 release

I have 10 doc tickets for 3.2. Out of 18, 4 in progress, and 3 still open. The rest is done. *In progress: * IMPALA-8133 IMPALA-8296 IMPALA-8297 IMPALA-7974 *Open:* IMPALA-8067 IMPALA-7718 IMPALA-8298 Thanks. alex On Mon, Mar 11, 2019 at 6:33 AM Gabor Kaszab wrote: > Thanks for the feedback!

Re: [DISCUSS] 3.2.0 release

>Similarly, if there is anything that is not ready but is right around the corner and you insist to include it to the release, let me know. IMPALA-6503 introduced a test error on S3, there is already a fix underway: https://gerrit.cloudera.org/#/c/12714/ Please wait for the fix to be merged and

Re: [DISCUSS] 3.2.0 release

Thanks for the feedback! No objections came agains the release so let me continue with the next steps. I see that the ORC complex types just got into the repo so I propose to cut the release there (inclusive): 9686545 IMPALA-6503: Support reading complex types from ORC In case there is anything

Re: [DISCUSS] 3.2.0 release

+1 - what Jim said! On Mon, Mar 4, 2019 at 9:53 AM Jim Apple wrote: > +1 to both a release and a habit of curated release notes as Quanlong > suggests. > > On Mon, Mar 4, 2019 at 6:54 AM Quanlong Huang > wrote: > > > > +1. Thanks for your volunteer! > > > > If we decide to release, could we

Re: [DISCUSS] 3.2.0 release

+1 to both a release and a habit of curated release notes as Quanlong suggests. On Mon, Mar 4, 2019 at 6:54 AM Quanlong Huang wrote: > > +1. Thanks for your volunteer! > > If we decide to release, could we manage a doc that everyone can write down > his/her notable works in this version? Got

Re: [DISCUSS] 3.2.0 release

+1. Thanks for your volunteer! If we decide to release, could we manage a doc that everyone can write down his/her notable works in this version? Got this idea from the Kudu community and feel it very helpful:

[DISCUSS] 3.2.0 release

Hey, 3.1.0 has been released at the beginning of December and I feel that since then there are a number of bug fixes and improvements checked in. What do you think about releasing 3.2.0 soon? I volunteer as a release manager in case no one is against. Cheers, Gabor