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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> > > wrote: > > > > > +1 - what Jim said! > > > > > > On Mon, Mar 4, 2019 at 9:53 AM Jim Apple <[email protected]> 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 < > [email protected] > > > > > > > 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 < > > [email protected] > > > > > > > > > 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 > > > > > > > > > > > > > > > >
