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 Mon, Mar 18, 2019 at 1:52 PM Jeszy <jes...@gmail.com> wrote: > 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 2.12 having a major impact on the scalability and > performance for most large scale users, but shows up as a bug called > 'KRPC milestone 1'. :) > It'd be great to be able to read through a page at most and have a > good idea of what actually happened in a release, from a functionality > and user point of view. > > Jeszy > > On Mon, Mar 18, 2019 at 1:50 PM Quanlong Huang <huangquanl...@gmail.com> > wrote: > > > > 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: > > - https://kudu.apache.org/docs/release_notes.html > > - > > > https://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_rn_new_in_cdh_516.html > > > > However, the "Kudu 1.9.0 Release Notes" we pasted above looks like a > draft. > > I think if we do so, we still need a document writer to polish and > > reorganize the doc. > > > > Thanks, > > Quanlong > > > > On Mon, Mar 18, 2019 at 8:23 PM Gabor Kaszab <gaborkas...@cloudera.com> > > wrote: > > > > > Hey, > > > > > > I recently had some time to give a second thought on the release notes > doc > > > idea proposed above. The link Quanlong attached brings me to this doc > that > > > contains a reduced list of features/bug fixes/ improvements and another > > > reduced list of the short descriptions of these: > > > > > > > https://docs.google.com/document/d/1eeL4sfXvRxHvA7PcUw3SH2vA_5grb9-kRtL06Kzm5Cw/edit > > > > > > We already have an official release notes that contain a list of all > the > > > changes in the release where you are one click away from reading the > > > details of a particular change. > > > https://impala.apache.org/docs/changelog-3.1.html > > > > > > All in all, currently I don't see the added value of creating another > > > release notes document. Any comments on this? > > > > > > Cheers, > > > Gabor > > > > > > > > > > > > On Mon, Mar 18, 2019 at 10:32 AM Gabor Kaszab < > gaborkas...@cloudera.com> > > > wrote: > > > > > > > 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> wrote: > > > > > > > >> 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 < > gaborkas...@cloudera.com> > > > >> wrote: > > > >> > > > >> > (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 > > > >> > - 9cc75c59d5a09bd8cccc98bdf05cc64a98a70ffd IMPALA-8133 > > > >> > - 535d286ee16721a35bda1861e4d011ea99a8c02f IMPALA-8067 > > > >> > - 0d3d3258d2762887c61bf8e64e5df33dc2419817 IMPALA-8298 > > > >> > - 668bb73e1153afcb50ffc8b45267232b926a2258 IMPALA-7974 > > > >> > - ca98d6649d700517e90359d39c94d3356c6c092e IMPALA-7718 > > > >> > > > > >> > Alex, I see 2 doc changes remaining according to your list. Do you > > > feel > > > >> > they can get to the repo in the next 1-2 days? I can wait for > them, > > > >> then. > > > >> > IMPALA-8296 > > > >> > IMPALA-8297 > > > >> > > > > >> > If no other request comes in until then, then I'll take the above > > > >> mentioned > > > >> > as the content of the 3.2.0 release and advance with the next > steps of > > > >> > release creation. > > > >> > > > > >> > Cheers, > > > >> > Gabor > > > >> > > > > >> > > > > >> > On Thu, Mar 14, 2019 at 1:18 PM Gabor Kaszab < > > > gaborkas...@cloudera.com> > > > >> > wrote: > > > >> > > > > >> > > 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 > > > >> > > < > > > >> > > > > >> > > > > https://github.com/apache/impala/commit/9686545bfd7236350d165813621bf783b42d1c18 > > > >> > > > > > >> > > (inclusive) > > > >> > > - As Csaba requested, I'll > > > >> > > include 26639963e0ea66bea716c0238cdf1ff086159c7c IMPALA-8300 to > > > >> correct a > > > >> > > test issue introduced by the commit right above. > > > >> > > - Alex sent in a number of doc commits covering changes that are > > > >> already > > > >> > > in, so I'll include them as well: > > > >> > > > > > >> > > > > > >> > > On Mon, Mar 11, 2019 at 6:54 PM Alexandra Rodoni < > > > >> arod...@cloudera.com> > > > >> > > wrote: > > > >> > > > > > >> > >> 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 < > > > >> gaborkas...@cloudera.com> > > > >> > >> wrote: > > > >> > >> > > > >> > >> > 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 before this commit that you are not > > > sure > > > >> and > > > >> > >> > prefer to omit from the release please let me know. > 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. > > > >> > >> > > > > >> > >> > From doc's perspective I'm curious how far we are from having > > > >> coverage > > > >> > >> for > > > >> > >> > the proposed changes. > > > >> > >> > > > > >> > >> > Having a release notes doc is a good idea. Once we agree on > the > > > >> > content > > > >> > >> > I'll create one and share it with the community so that each > > > >> > contributor > > > >> > >> > can fill in their change's description. > > > >> > >> > > > > >> > >> > Cheers, > > > >> > >> > Gabor > > > >> > >> > > > > >> > >> > > > > >> > >> > On Mon, Mar 4, 2019 at 11:28 PM Tim Armstrong < > > > >> > tarmstr...@cloudera.com> > > > >> > >> > wrote: > > > >> > >> > > > > >> > >> > > +1 - what Jim said! > > > >> > >> > > > > > >> > >> > > On Mon, Mar 4, 2019 at 9:53 AM Jim Apple < > jbap...@cloudera.com > > > > > > > >> > >> 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 < > > > >> > >> huangquanl...@gmail.com > > > >> > >> > > > > > >> > >> > > > 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 this idea > from > > > the > > > >> > Kudu > > > >> > >> > > > > community and feel it very helpful: > > > >> > >> > > > > > > > >> > >> > > > > > > >> > >> > > > > > >> > >> > > > > >> > >> > > > >> > > > > >> > > > > https://lists.apache.org/thread.html/8a10a4d244369f43b97c79513f13766c393a98252d3a2dade7611cc3@%3Cdev.kudu.apache.org%3E > > > >> > >> > > > > > > > >> > >> > > > > Thanks, > > > >> > >> > > > > Quanlong > > > >> > >> > > > > > > > >> > >> > > > > On Mon, Mar 4, 2019 at 10:18 PM Gabor Kaszab < > > > >> > >> > gaborkas...@cloudera.com > > > >> > >> > > > > > > >> > >> > > > > wrote: > > > >> > >> > > > > > > > >> > >> > > > > > 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 > > > >> > >> > > > > > > > > >> > >> > > > > > > >> > >> > > > > > >> > >> > > > > >> > >> > > > >> > > > > > >> > > > > >> > > > > > > > >
