Re: Druid 0.12.1-rc1 vote

[Julian Hyde]

You should make it clear that this is a non-ASF release. Such releases are 
allowed during incubation but not encouraged.

Also be sure to mention it in your next report.

Julian


> On Apr 24, 2018, at 2:49 PM, Jihoon Son  wrote:
> 
> Hi all,
> 
> We currently have no open issues/PRs for 0.12.1 (
> https://github.com/druid-io/druid/milestone/26), so I created a branch for
> 0.12.1 (https://github.com/druid-io/druid/tree/0.12.1).
> 
> Let's vote on releasing RC1. Here is my +1.
> 
> Best,
> Jihoon


-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org

Re: Dev list migration

[Julian Hyde]

You should also update https://github.com/druid-io/druid/blob/master/README.md 
.


> On Apr 24, 2018, at 8:08 AM, Gian Merlino  wrote:
> 
> Today (well, yesterday) is the day we had decided on for migrating the dev
> list. If there are no objections I'll update the community page, send out
> another note to the old list, and put the old list into read only mode.
> 
> On Tue, Apr 17, 2018 at 8:28 PM, Himanshu  wrote:
> 
>> +1
>> 
>> On Tue, Apr 17, 2018 at 3:20 PM, Nishant Bangarwa <
>> nbanga...@hortonworks.com
>>> wrote:
>> 
>>> +1
>>> --
>>> Nishant Bangarwa
>>> Hortonworks
>>> (M): +91-9729200044
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 4/17/18, 10:19 PM, "Jonathan Wei"  wrote:
>>> 
 +1
 
 On 2018/04/17 18:09:37, David Lim  wrote:
> +1
> 
> On Tue, Apr 17, 2018 at 11:49 AM, Gian Merlino 
>> wrote:
> 
>> Hi all,
>> 
>> In the dev sync today there was some general agreement around
>>> migrating the
>> dev list to Apache next week. Please +1 or -1 in this thread as
>>> desired.
>> 
>> I think ideally we'd want an autoresponder but I don't see a way to
>>> set
>> one. So the concrete plan I'd propose instead is to do the following
>>> next
>> Monday, April 23,
>> 
>> 1) Post a message to the list that we have migrated to
>> dev@druid.apache.org
>> 2) Sticky that post on
>> https://groups.google.com/forum/#!forum/druid-development
>> 3) Update the list link on the web site at
>> http://druid.io/community/
>> 4) Disable posting on druid-developm...@googlegroups.com
>> 
>> This message has been cross posted to both lists, but please reply
>> on
>>> the
>> Apache list. If you haven't signed up for it yet, you can do that by
>> emailing dev-subscr...@druid.apache.org.
>> 
> 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
 For additional commands, e-mail: dev-h...@druid.apache.org
 
>>> 
>> 

Druid 0.12.1-rc1 vote

[Jihoon Son]

Hi all,

We currently have no open issues/PRs for 0.12.1 (
https://github.com/druid-io/druid/milestone/26), so I created a branch for
0.12.1 (https://github.com/druid-io/druid/tree/0.12.1).

Let's vote on releasing RC1. Here is my +1.

Best,
Jihoon

Re: Dependencies licenses Report

[Gian Merlino]

> you are sure about this? thought the donation paper work is signed right?

Not yet as far as I know; last I heard was a week or so ago.

On Tue, Apr 24, 2018 at 1:41 PM, Slim Bouguerra 
wrote:

>
> > On Apr 24, 2018, at 1:18 PM, Gian Merlino  wrote:
> >
> > Do you mean the license headers?
>
> Yes, did quick run and was complaining first about our headers and also
> some of the other files without any headers.
>
> > Those, I think, we shouldn't change until
> > the code is imported into Apache.
>
> you are sure about this? thought the donation paper work is signed right?
>
> >
> > If it's possible to use Rat to audit dependency licenses without looking
> at
> > the license headers of our own files, that would still be useful at this
> > point.
>
> Not sure but will look.
>
> >
> > On Tue, Apr 24, 2018 at 12:57 PM, Slim Bouguerra 
> wrote:
> >
> >>
> >> I Think the first step to use RAT is to reformat all the Druid code
> >> licenses.
> >> Any idea if this can be done now or we need some legal work to be done?
> >>
> >> On 2018/04/20 17:52:46, Slim Bouguerra 
> wrote:
> >>> As Suggested above, RAT is used as a first filter that does most of the
> >>> checking but it is not 100% enough.
> >>> The mvn site plugin is used to collect list of dependencies but it is
> not
> >>> enough as well.
> >>> They manually edit/create the Licenses/Notice files. It is done by
> >>> hand/a_human to avoid any glitch that an automatic tool will introduce
> >> and
> >>> to insure that someone has looked at it.
> >>> Seems like it is time consuming the first time but then it should be
> >>> incremental thus not that hard.
> >>>
> >>>
> >>>
> >>> On Wed, Apr 18, 2018 at 8:45 AM, Julian Hyde 
> >> wrote:
> >>>
>  The main tool to use is Apache RAT. Definitely use that.
> 
>  One of the hardest tasks is getting the contents of LICENSE and NOTICE
>  right. That is a manual task I’m afraid.
> 
>  Julian
> 
> > On Apr 18, 2018, at 08:34, Gian Merlino 
> >> wrote:
> >
> > Hi Slim,
> >
> > Do you know if ORC & Hive use this tool as part of their release
> >> process?
> > And if it's considered a good tool by itself for verifying we meet
> >> all of
> > the Apache licensing requirements, or if we'll need something else
> >> too?
> >
> >> On Tue, Apr 17, 2018 at 9:15 PM, Slim Bouguerra 
>  wrote:
> >>
> >> One of the question last dev synch was about the generation of
>  dependency
> >> licenses.
> >> Some projects (ORC and Hive) use the maven site plugin that can
>  generates
> >> reports with all the dependencies and licenses details.
> >> I have run it on Druid and this is how it looks for Druid Api
> >> Module.
> >> cmd
> >>
> >> mvn project-info-reports:dependencies
> >>
> >> The site directory can be found under target/site
> >> here is an example for one module
> >> https://drive.google.com/file/d/1P8R0kZjp8zP4WSOVrKdlJF7Xr8-
> >> OI7Oe/view?usp=sharing
> >>
> >> Also no fancy tools used to detect unwanted licenses, it is done
> >> while
> >> reviewing PR
> >>
> >>
> >>
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> >> For additional commands, e-mail: dev-h...@druid.apache.org
> >>
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
>  For additional commands, e-mail: dev-h...@druid.apache.org
> 
> 
> >>>
> >>>
> >>> --
> >>>
> >>> B-Slim
> >>> ___/\/\/\___/\/\/\___/\/\/\___/\/\/\___/
> \/\/\___
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> >> For additional commands, e-mail: dev-h...@druid.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> For additional commands, e-mail: dev-h...@druid.apache.org
>
>

Re: Dependencies licenses Report

[Gian Merlino]

Do you mean the license headers? Those, I think, we shouldn't change until
the code is imported into Apache.

If it's possible to use Rat to audit dependency licenses without looking at
the license headers of our own files, that would still be useful at this
point.

On Tue, Apr 24, 2018 at 12:57 PM, Slim Bouguerra  wrote:

>
> I Think the first step to use RAT is to reformat all the Druid code
> licenses.
> Any idea if this can be done now or we need some legal work to be done?
>
> On 2018/04/20 17:52:46, Slim Bouguerra  wrote:
> > As Suggested above, RAT is used as a first filter that does most of the
> > checking but it is not 100% enough.
> > The mvn site plugin is used to collect list of dependencies but it is not
> > enough as well.
> > They manually edit/create the Licenses/Notice files. It is done by
> > hand/a_human to avoid any glitch that an automatic tool will introduce
> and
> > to insure that someone has looked at it.
> > Seems like it is time consuming the first time but then it should be
> > incremental thus not that hard.
> >
> >
> >
> > On Wed, Apr 18, 2018 at 8:45 AM, Julian Hyde 
> wrote:
> >
> > > The main tool to use is Apache RAT. Definitely use that.
> > >
> > > One of the hardest tasks is getting the contents of LICENSE and NOTICE
> > > right. That is a manual task I’m afraid.
> > >
> > > Julian
> > >
> > > > On Apr 18, 2018, at 08:34, Gian Merlino 
> wrote:
> > > >
> > > > Hi Slim,
> > > >
> > > > Do you know if ORC & Hive use this tool as part of their release
> process?
> > > > And if it's considered a good tool by itself for verifying we meet
> all of
> > > > the Apache licensing requirements, or if we'll need something else
> too?
> > > >
> > > >> On Tue, Apr 17, 2018 at 9:15 PM, Slim Bouguerra 
> > > wrote:
> > > >>
> > > >> One of the question last dev synch was about the generation of
> > > dependency
> > > >> licenses.
> > > >> Some projects (ORC and Hive) use the maven site plugin that can
> > > generates
> > > >> reports with all the dependencies and licenses details.
> > > >> I have run it on Druid and this is how it looks for Druid Api
> Module.
> > > >> cmd
> > > >>
> > > >> mvn project-info-reports:dependencies
> > > >>
> > > >> The site directory can be found under target/site
> > > >> here is an example for one module
> > > >> https://drive.google.com/file/d/1P8R0kZjp8zP4WSOVrKdlJF7Xr8-
> > > >> OI7Oe/view?usp=sharing
> > > >>
> > > >> Also no fancy tools used to detect unwanted licenses, it is done
> while
> > > >> reviewing PR
> > > >>
> > > >>
> > > >>
> > > >> 
> -
> > > >> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> > > >> For additional commands, e-mail: dev-h...@druid.apache.org
> > > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> > > For additional commands, e-mail: dev-h...@druid.apache.org
> > >
> > >
> >
> >
> > --
> >
> > B-Slim
> > ___/\/\/\___/\/\/\___/\/\/\___/\/\/\___/\/\/\___
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> For additional commands, e-mail: dev-h...@druid.apache.org
>
>

Re: Sync-up today

[Jonathan Wei]

Hangouts link:

https://hangouts.google.com/hangouts/_/imply.io/druid-dev-sync

On 2018/04/24 15:20:06, Jonathan Wei  wrote: 
> I can host it today
> 
> On 2018/04/24 14:20:13, Charles Allen  wrote: 
> > Is some one else able to start the sync-up today? I will be unable to make
> > it again.
> > 
> > Thank you,
> > Charles Allen
> > 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> For additional commands, e-mail: dev-h...@druid.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org

Re: Sync-up today

[Jonathan Wei]

I can host it today

On 2018/04/24 14:20:13, Charles Allen  wrote: 
> Is some one else able to start the sync-up today? I will be unable to make
> it again.
> 
> Thank you,
> Charles Allen
> 

-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org

Re: Dev list migration

[Gian Merlino]

Today (well, yesterday) is the day we had decided on for migrating the dev
list. If there are no objections I'll update the community page, send out
another note to the old list, and put the old list into read only mode.

On Tue, Apr 17, 2018 at 8:28 PM, Himanshu  wrote:

> +1
>
> On Tue, Apr 17, 2018 at 3:20 PM, Nishant Bangarwa <
> nbanga...@hortonworks.com
> > wrote:
>
> > +1
> > --
> > Nishant Bangarwa
> > Hortonworks
> > (M): +91-9729200044
> >
> >
> >
> >
> >
> >
> >
> > On 4/17/18, 10:19 PM, "Jonathan Wei"  wrote:
> >
> > >+1
> > >
> > >On 2018/04/17 18:09:37, David Lim  wrote:
> > >> +1
> > >>
> > >> On Tue, Apr 17, 2018 at 11:49 AM, Gian Merlino 
> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > In the dev sync today there was some general agreement around
> > migrating the
> > >> > dev list to Apache next week. Please +1 or -1 in this thread as
> > desired.
> > >> >
> > >> > I think ideally we'd want an autoresponder but I don't see a way to
> > set
> > >> > one. So the concrete plan I'd propose instead is to do the following
> > next
> > >> > Monday, April 23,
> > >> >
> > >> > 1) Post a message to the list that we have migrated to
> > >> > dev@druid.apache.org
> > >> > 2) Sticky that post on
> > >> > https://groups.google.com/forum/#!forum/druid-development
> > >> > 3) Update the list link on the web site at
> http://druid.io/community/
> > >> > 4) Disable posting on druid-developm...@googlegroups.com
> > >> >
> > >> > This message has been cross posted to both lists, but please reply
> on
> > the
> > >> > Apache list. If you haven't signed up for it yet, you can do that by
> > >> > emailing dev-subscr...@druid.apache.org.
> > >> >
> > >>
> > >
> > >-
> > >To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> > >For additional commands, e-mail: dev-h...@druid.apache.org
> > >
> >
>

Sync-up today

[Charles Allen]

Is some one else able to start the sync-up today? I will be unable to make
it again.

Thank you,
Charles Allen