+1. I concur with Tim that it's safer to leave out this commit <https://github.com/apache/impala/commit/5391100c7eeb33193de7861e761c3920f1d1eecc> 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 <jbap...@cloudera.com> wrote: > +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 <tarmstr...@cloudera.com> > wrote: > > > +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: > > https://issues.apache.org/jira/issues/?filter=12345062 > > > > We should figure out the best branching point. Most of the recent commits > > should go into the release but there are a few larger changes that we > might > > want to take on a case-by-case basis. E.g. I'm not sure if Michael Ho > wants > > to give some of the RPC changes more time to bake or not. > > > > Cheers, > > Tim > > > > On Mon, Nov 5, 2018 at 6:51 AM Zoltan Borok-Nagy < > borokna...@cloudera.com> > > wrote: > > > > > 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 and let the community know if anyone has any > > > objections to this. > > > > > > Thanks, > > > Zoltan > > > > > > -- Thanks, Michael
