You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@druid.apache.org by Gian Merlino <gi...@apache.org> on 2019/01/04 21:06:40 UTC
Druid 0.14 timing
It feels like 0.13.0 was just recently released, but it was branched off
back in October, and it has almost been 3 months since then. How do we feel
about doing an 0.14 branch cut at the end of January (Thu Jan 31) - going
back to the every 3 months cycle?
For this release, based on the feedback we got from the Incubator vote last
time, we'll need to fix up the LICENSE and NOTICE issues that were flagged
but waved through for our first release. (Justin said he would have -1'd
based on that if it was anything beyond a first release.)
Re: Druid 0.14 timing
Posted by David Lim <da...@apache.org>.
+1
I see no reason to deviate from our 3 month cycle. Cutting another release
soon will also be good for continuing to make progress towards Apache
graduation.
On Fri, Jan 4, 2019 at 4:00 PM Fangjin Yang <fa...@imply.io> wrote:
> +1
>
> On Fri, Jan 4, 2019 at 1:52 PM Jihoon Son <ji...@apache.org> wrote:
>
> > +1 sounds good to me.
> >
> > Jihoon
> >
> > On Fri, Jan 4, 2019 at 1:06 PM Gian Merlino <gi...@apache.org> wrote:
> >
> > > It feels like 0.13.0 was just recently released, but it was branched
> off
> > > back in October, and it has almost been 3 months since then. How do we
> > feel
> > > about doing an 0.14 branch cut at the end of January (Thu Jan 31) -
> going
> > > back to the every 3 months cycle?
> > >
> > > For this release, based on the feedback we got from the Incubator vote
> > last
> > > time, we'll need to fix up the LICENSE and NOTICE issues that were
> > flagged
> > > but waved through for our first release. (Justin said he would have
> -1'd
> > > based on that if it was anything beyond a first release.)
> > >
> >
>
Re: Druid 0.14 timing
Posted by Fangjin Yang <fa...@imply.io>.
+1
On Fri, Jan 4, 2019 at 1:52 PM Jihoon Son <ji...@apache.org> wrote:
> +1 sounds good to me.
>
> Jihoon
>
> On Fri, Jan 4, 2019 at 1:06 PM Gian Merlino <gi...@apache.org> wrote:
>
> > It feels like 0.13.0 was just recently released, but it was branched off
> > back in October, and it has almost been 3 months since then. How do we
> feel
> > about doing an 0.14 branch cut at the end of January (Thu Jan 31) - going
> > back to the every 3 months cycle?
> >
> > For this release, based on the feedback we got from the Incubator vote
> last
> > time, we'll need to fix up the LICENSE and NOTICE issues that were
> flagged
> > but waved through for our first release. (Justin said he would have -1'd
> > based on that if it was anything beyond a first release.)
> >
>
Re: Druid 0.14 timing
Posted by Jihoon Son <ji...@apache.org>.
+1 sounds good to me.
Jihoon
On Fri, Jan 4, 2019 at 1:06 PM Gian Merlino <gi...@apache.org> wrote:
> It feels like 0.13.0 was just recently released, but it was branched off
> back in October, and it has almost been 3 months since then. How do we feel
> about doing an 0.14 branch cut at the end of January (Thu Jan 31) - going
> back to the every 3 months cycle?
>
> For this release, based on the feedback we got from the Incubator vote last
> time, we'll need to fix up the LICENSE and NOTICE issues that were flagged
> but waved through for our first release. (Justin said he would have -1'd
> based on that if it was anything beyond a first release.)
>
Re: Druid 0.14 timing
Posted by Gian Merlino <gi...@apache.org>.
Sounds good to me - thanks Jon.
On Sun, Feb 3, 2019 at 4:49 PM Jonathan Wei <jo...@apache.org> wrote:
> Hi all,
>
> It's around the discussed time for the release; I'm planning on cutting the
> 0.14.0 branch tomorrow, and I'll volunteer to serve as the release manager
> for 0.14.0.
>
> Thanks,
> Jon
>
> On Mon, Jan 7, 2019 at 5:50 PM Benedict Jin <be...@gmail.com>
> wrote:
>
> >
> >
> > On 2019/01/04 21:06:40, Gian Merlino <gi...@apache.org> wrote:
> > > It feels like 0.13.0 was just recently released, but it was branched
> off
> > > back in October, and it has almost been 3 months since then. How do we
> > feel
> > > about doing an 0.14 branch cut at the end of January (Thu Jan 31) -
> going
> > > back to the every 3 months cycle?
> > >
> > > For this release, based on the feedback we got from the Incubator vote
> > last
> > > time, we'll need to fix up the LICENSE and NOTICE issues that were
> > flagged
> > > but waved through for our first release. (Justin said he would have
> -1'd
> > > based on that if it was anything beyond a first release.)
> > > +1
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
> > For additional commands, e-mail: dev-help@druid.apache.org
> >
> >
>
Re: Druid 0.14 timing
Posted by Jonathan Wei <jo...@apache.org>.
Hi all,
It's around the discussed time for the release; I'm planning on cutting the
0.14.0 branch tomorrow, and I'll volunteer to serve as the release manager
for 0.14.0.
Thanks,
Jon
On Mon, Jan 7, 2019 at 5:50 PM Benedict Jin <be...@gmail.com>
wrote:
>
>
> On 2019/01/04 21:06:40, Gian Merlino <gi...@apache.org> wrote:
> > It feels like 0.13.0 was just recently released, but it was branched off
> > back in October, and it has almost been 3 months since then. How do we
> feel
> > about doing an 0.14 branch cut at the end of January (Thu Jan 31) - going
> > back to the every 3 months cycle?
> >
> > For this release, based on the feedback we got from the Incubator vote
> last
> > time, we'll need to fix up the LICENSE and NOTICE issues that were
> flagged
> > but waved through for our first release. (Justin said he would have -1'd
> > based on that if it was anything beyond a first release.)
> > +1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
> For additional commands, e-mail: dev-help@druid.apache.org
>
>
Re: Druid 0.14 timing
Posted by Benedict Jin <be...@gmail.com>.
On 2019/01/04 21:06:40, Gian Merlino <gi...@apache.org> wrote:
> It feels like 0.13.0 was just recently released, but it was branched off
> back in October, and it has almost been 3 months since then. How do we feel
> about doing an 0.14 branch cut at the end of January (Thu Jan 31) - going
> back to the every 3 months cycle?
>
> For this release, based on the feedback we got from the Incubator vote last
> time, we'll need to fix up the LICENSE and NOTICE issues that were flagged
> but waved through for our first release. (Justin said he would have -1'd
> based on that if it was anything beyond a first release.)
> +1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
For additional commands, e-mail: dev-help@druid.apache.org