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 revert the risky commits on the
release branch
Do we have any other commits that we want to leave out?
Thanks for the link, Tim. I think normally we should wait for all the
blockers, right? However, on a few of them there were no recent activity.
Do we know the exact list of Jiras we want to wait on? Please speak up if
you are working on a Jira that you want to push into 3.1.
Alex: I don't think we can start the process this week. It'd be great if we
could start it next week. However, it largely depends on the progress of
the ongoing activities.
Thanks,
Zoltan
On Mon, Nov 5, 2018 at 8:12 PM Alexandra Rodoni <arod...@cloudera.com>
wrote:
> 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 <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
> >
>
