You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@druid.apache.org by Clint Wylie <cw...@apache.org> on 2019/08/22 20:05:21 UTC
0.16.0-incubating
Hi everyone,
Just a heads up that I'm planning on branching 0.16.0-incubating off of
master at the end of the week, is there anything that *needs* to be
included that is not already part of the milestone so we can get it added
and prioritize review?
Thanks,
Clint
Re: 0.16.0-incubating
Posted by Clint Wylie <cw...@apache.org>.
I've created the 0.16.0-incubating branch and will try to get a release
candidate built and up for testing/voting as soon as possible.
On Fri, Aug 23, 2019 at 4:09 AM Dylan Wylie <dy...@apache.org> wrote:
> Hey all,
>
> This causes (what seems to be) a key JAR to be missing from the build -
> https://github.com/apache/incubator-druid/issues/8338
>
> It could well be something weird in our setup & since we're not seeing
> anyone else reporting it, that seems likely. Anyone able to triage the
> issue & my suggested fix?
>
> Cheers,
> Dylan
>
>
> On Thu, 22 Aug 2019 at 21:05, Clint Wylie <cw...@apache.org> wrote:
>
> > Hi everyone,
> >
> > Just a heads up that I'm planning on branching 0.16.0-incubating off of
> > master at the end of the week, is there anything that *needs* to be
> > included that is not already part of the milestone so we can get it added
> > and prioritize review?
> >
> > Thanks,
> > Clint
> >
>
Re: 0.16.0-incubating
Posted by Dylan Wylie <dy...@apache.org>.
Hey all,
This causes (what seems to be) a key JAR to be missing from the build -
https://github.com/apache/incubator-druid/issues/8338
It could well be something weird in our setup & since we're not seeing
anyone else reporting it, that seems likely. Anyone able to triage the
issue & my suggested fix?
Cheers,
Dylan
On Thu, 22 Aug 2019 at 21:05, Clint Wylie <cw...@apache.org> wrote:
> Hi everyone,
>
> Just a heads up that I'm planning on branching 0.16.0-incubating off of
> master at the end of the week, is there anything that *needs* to be
> included that is not already part of the milestone so we can get it added
> and prioritize review?
>
> Thanks,
> Clint
>