Re: Druid repo migration plan

2018-06-21 Thread Maxime Beauchemin
+1

Note that usually we would expect voting thread to have a `[VOTE]` prefix
in the the email subject.

Max

On Thu, Jun 21, 2018 at 12:26 AM David Lim  wrote:

> +1
>
> On Thu, Jun 21, 2018 at 12:55 AM, Himanshu  wrote:
>
> > +1 ... Major milestone, thanks
> >
> > On Wed, Jun 20, 2018, 9:13 PM Gian Merlino,  wrote:
> >
> > > +1; thanks Jon!
> > >
> > > On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son 
> wrote:
> > >
> > > > +1
> > > >
> > > > Sounds good to me.
> > > >
> > > > Jihoon
> > > >
> > > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa <
> > > > nbanga...@hortonworks.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > --
> > > > > Nishant Bangarwa
> > > > >
> > > > > Hortonworks
> > > > >
> > > > > On 6/20/18, 3:57 PM, "Jonathan Wei"  wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > The SGA for Druid has been sorted out, we can get started on
> > > > migrating
> > > > > the
> > > > > old Github repo to Apache.
> > > > >
> > > > > Based on the discussion in our previous migration thread (
> > > > >
> > > > >
> > > >
> > > https://groups.google.com/forum/#!msg/druid-development/
> > q1ip-L8xpBk/GPK1LhC7BQAJ
> > > > > ),
> > > > > it seems we favor using our existing Github PR and issues
> > > workflows.
> > > > >
> > > > > I'll file a JIRA ticket requesting transfer of
> > > > > https://github.com/druid-io/druid to a Gitbox-style Apache
> repo,
> > > > > keeping
> > > > > the existing history of PRs/issues/stars/etc. (e.g., Superset:
> > > > > https://github.com/apache/incubator-superset)
> > > > >
> > > > > Before I do that, I wanted to open this thread for a vote to
> > > confirm
> > > > > that
> > > > > we're all okay with this plan, so please chime in with an
> > approval
> > > or
> > > > > any
> > > > > concerns that you may have.
> > > > >
> > > > > Thanks,
> > > > > Jon
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>


Re: Druid repo migration plan

2018-06-21 Thread David Lim
+1

On Thu, Jun 21, 2018 at 12:55 AM, Himanshu  wrote:

> +1 ... Major milestone, thanks
>
> On Wed, Jun 20, 2018, 9:13 PM Gian Merlino,  wrote:
>
> > +1; thanks Jon!
> >
> > On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son  wrote:
> >
> > > +1
> > >
> > > Sounds good to me.
> > >
> > > Jihoon
> > >
> > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa <
> > > nbanga...@hortonworks.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > --
> > > > Nishant Bangarwa
> > > >
> > > > Hortonworks
> > > >
> > > > On 6/20/18, 3:57 PM, "Jonathan Wei"  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > The SGA for Druid has been sorted out, we can get started on
> > > migrating
> > > > the
> > > > old Github repo to Apache.
> > > >
> > > > Based on the discussion in our previous migration thread (
> > > >
> > > >
> > >
> > https://groups.google.com/forum/#!msg/druid-development/
> q1ip-L8xpBk/GPK1LhC7BQAJ
> > > > ),
> > > > it seems we favor using our existing Github PR and issues
> > workflows.
> > > >
> > > > I'll file a JIRA ticket requesting transfer of
> > > > https://github.com/druid-io/druid to a Gitbox-style Apache repo,
> > > > keeping
> > > > the existing history of PRs/issues/stars/etc. (e.g., Superset:
> > > > https://github.com/apache/incubator-superset)
> > > >
> > > > Before I do that, I wanted to open this thread for a vote to
> > confirm
> > > > that
> > > > we're all okay with this plan, so please chime in with an
> approval
> > or
> > > > any
> > > > concerns that you may have.
> > > >
> > > > Thanks,
> > > > Jon
> > > >
> > > >
> > > >
> > >
> >
>


Re: Considering 0.12.2 release

2018-06-21 Thread Gian Merlino
I think we're hoping that the next major (0.13) will also be our first
Apache release. If it ends up taking too long we might want to rethink that
but hopefully it won't (see the recently started thread about the next
step, migrating the Github repos).

On Wed, Jun 20, 2018 at 10:42 PM Roman Leventov 
wrote:

> Why won't release 13.0 instead (as non-Apache)?
>
> On Thu, 21 Jun 2018, 08:18 Gian Merlino,  wrote:
>
> > +1
> >
> > I would suggest adding these two as well.
> >
> > https://github.com/druid-io/druid/pull/5878 - Fix inefficient available
> > segment cache population in SQLMetadataSegmentManager.
> > https://github.com/druid-io/druid/pull/5873 - HdfsDataSegmentPusher:
> Close
> > tmpIndexFile before copying it.
> >
> > On Tue, Jun 12, 2018 at 11:34 AM Prashant Deva 
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Jun 8, 2018 at 3:37 PM Jihoon Son 
> wrote:
> > >
> > > > Hi guys,
> > > >
> > > > we have a couple of bug fix PRs available and some of them fix
> > regression
> > > > bugs.
> > > >
> > > > Here is the list of currently available bug fix PRs which are not
> > > included
> > > > in 0.12.1.
> > > >
> > > > Regression bug fixes
> > > > - https://github.com/druid-io/druid/pull/5858
> > > > - https://github.com/druid-io/druid/pull/5805
> > > > - https://github.com/druid-io/druid/pull/5807
> > > >
> > > > Non-regression bug fixes
> > > > - https://github.com/druid-io/druid/pull/5850
> > > > - https://github.com/druid-io/druid/pull/5815
> > > > - https://github.com/druid-io/druid/pull/5856
> > > >
> > > > I think it's worth to make another release for users.
> > > >
> > > > Welcome any idea.
> > > >
> > > > Jihoon
> > > >
> > > --
> > > Prashant
> > >
> >
>


Re: Druid repo migration plan

2018-06-21 Thread Himanshu
+1 ... Major milestone, thanks

On Wed, Jun 20, 2018, 9:13 PM Gian Merlino,  wrote:

> +1; thanks Jon!
>
> On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son  wrote:
>
> > +1
> >
> > Sounds good to me.
> >
> > Jihoon
> >
> > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa <
> > nbanga...@hortonworks.com>
> > wrote:
> >
> > > +1
> > >
> > > --
> > > Nishant Bangarwa
> > >
> > > Hortonworks
> > >
> > > On 6/20/18, 3:57 PM, "Jonathan Wei"  wrote:
> > >
> > > Hi all,
> > >
> > > The SGA for Druid has been sorted out, we can get started on
> > migrating
> > > the
> > > old Github repo to Apache.
> > >
> > > Based on the discussion in our previous migration thread (
> > >
> > >
> >
> https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ
> > > ),
> > > it seems we favor using our existing Github PR and issues
> workflows.
> > >
> > > I'll file a JIRA ticket requesting transfer of
> > > https://github.com/druid-io/druid to a Gitbox-style Apache repo,
> > > keeping
> > > the existing history of PRs/issues/stars/etc. (e.g., Superset:
> > > https://github.com/apache/incubator-superset)
> > >
> > > Before I do that, I wanted to open this thread for a vote to
> confirm
> > > that
> > > we're all okay with this plan, so please chime in with an approval
> or
> > > any
> > > concerns that you may have.
> > >
> > > Thanks,
> > > Jon
> > >
> > >
> > >
> >
>