+1
Op do 5 dec. 2019 om 04:35 schreef Kurt Young
> +1
>
>
>
> On Thu, Dec 5, 2019 at 9:47 AM Xavier Léauté wrote:
>
> > +1
> >
> > On Wed, Dec 4, 2019 at 5:28 PM Benedict Jin
> > wrote:
> >
> > > +1
> > >
> > > On 2019/12/04 21:33:00, Clint Wylie wrote:
> > > > +1
> > > >
> > > > On Wed, Dec
+1
On Thu, Dec 5, 2019 at 9:47 AM Xavier Léauté wrote:
> +1
>
> On Wed, Dec 4, 2019 at 5:28 PM Benedict Jin
> wrote:
>
> > +1
> >
> > On 2019/12/04 21:33:00, Clint Wylie wrote:
> > > +1
> > >
> > > On Wed, Dec 4, 2019 at 1:21 PM Jihoon Son
> wrote:
> > >
> > > > +1
> > > >
> > > > On Wed,
+1
On Wed, Dec 4, 2019 at 5:28 PM Benedict Jin
wrote:
> +1
>
> On 2019/12/04 21:33:00, Clint Wylie wrote:
> > +1
> >
> > On Wed, Dec 4, 2019 at 1:21 PM Jihoon Son wrote:
> >
> > > +1
> > >
> > > On Wed, Dec 4, 2019 at 1:20 PM Furkan KAMACI
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > +1!
>
+1
On 2019/12/04 21:33:00, Clint Wylie wrote:
> +1
>
> On Wed, Dec 4, 2019 at 1:21 PM Jihoon Son wrote:
>
> > +1
> >
> > On Wed, Dec 4, 2019 at 1:20 PM Furkan KAMACI
> > wrote:
> >
> > > Hi,
> > >
> > > +1!
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > 4 Ara 2019 Çar, saat 23:58
This sounds great to me. Thanks Jon.
On Wed, Dec 4, 2019 at 1:42 PM Jonathan Wei wrote:
> Hi all,
>
> Since it's been ~3 months since our last major release (0.16.0 released on
> Sep. 24, branch created Aug. 27), I propose creating the 0.17.0 branch from
> master next Monday (Dec. 9).
>
> I can
Hi all,
Since it's been ~3 months since our last major release (0.16.0 released on
Sep. 24, branch created Aug. 27), I propose creating the 0.17.0 branch from
master next Monday (Dec. 9).
I can volunteer to be the release manager for 0.17.0.
Thanks,
Jon
+1
On Wed, Dec 4, 2019 at 1:21 PM Jihoon Son wrote:
> +1
>
> On Wed, Dec 4, 2019 at 1:20 PM Furkan KAMACI
> wrote:
>
> > Hi,
> >
> > +1!
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > 4 Ara 2019 Çar, saat 23:58 tarihinde David Lim
> şunu
> > yazdı:
> >
> > > +1
> > >
> > > On Wed, Dec 4,
+1
On Wed, Dec 4, 2019 at 1:20 PM Furkan KAMACI wrote:
> Hi,
>
> +1!
>
> Kind Regards,
> Furkan KAMACI
>
> 4 Ara 2019 Çar, saat 23:58 tarihinde David Lim şunu
> yazdı:
>
> > +1
> >
> > On Wed, Dec 4, 2019 at 1:47 PM Fangjin Yang wrote:
> >
> > > +1
> > >
> > > On Wed, Dec 4, 2019 at 12:36 PM
Hi,
+1!
Kind Regards,
Furkan KAMACI
4 Ara 2019 Çar, saat 23:58 tarihinde David Lim şunu
yazdı:
> +1
>
> On Wed, Dec 4, 2019 at 1:47 PM Fangjin Yang wrote:
>
> > +1
> >
> > On Wed, Dec 4, 2019 at 12:36 PM Julian Hyde wrote:
> >
> > > +1
> > >
> > >
> > > > On Dec 4, 2019, at 12:19 PM, Gian
+1
On Wed, Dec 4, 2019 at 1:47 PM Fangjin Yang wrote:
> +1
>
> On Wed, Dec 4, 2019 at 12:36 PM Julian Hyde wrote:
>
> > +1
> >
> >
> > > On Dec 4, 2019, at 12:19 PM, Gian Merlino wrote:
> > >
> > > Earlier this year, Druid voted to graduate to a top level project. The
> > vote
> > > passed
+1 (binding)
src package:
- verified signature/hash
- compared source distribution contents against git tag (144bd78)
- LICENSE, NOTICE, and DISCLAIMER are present
- unit tests passed
- licenses checked
- built binary distribution
- ran quickstart
bin package:
- verified signature/hash
-
+1
On Wed, Dec 4, 2019 at 12:36 PM Julian Hyde wrote:
> +1
>
>
> > On Dec 4, 2019, at 12:19 PM, Gian Merlino wrote:
> >
> > Earlier this year, Druid voted to graduate to a top level project. The
> vote
> > passed and a resolution was submitted to the Board, but needed to be
> > shelved at the
That wording sounds good to me for the first section, I've updated the wiki
with it
On Wed, Dec 4, 2019 at 12:20 PM Gian Merlino wrote:
> By the way, I've just started a graduation VOTE on the dev list.
>
> On Wed, Dec 4, 2019 at 12:12 PM Gian Merlino wrote:
>
> > That is fair, I suggest we
Earlier this year, Druid voted to graduate to a top level project. The vote
passed and a resolution was submitted to the Board, but needed to be
shelved at the last minute. We are now ready to proceed to graduation once
again, and so I would like to call another vote.
For reference, our last vote
That is fair, I suggest we change the first section (issues remaining) to
this then:
> The project is not aware of any issues blocking graduation. Druid
previously shelved a resolution to graduate due to a potential brand issue,
which the project has since been working on with VP Brand. It is now
Hi,
> Druid plans to graduate, so I hope there aren’t 3 items!
There the report should state this.
> My comment on the proposed report is that it doesn’t mention the graduation
> resolution. It should also say that why the resolution was previously shelved
> - IP issues that have now been
Hi Justin,
I think it's fair to say that there aren't any unfinished issues, so it
makes sense for the section to be blank. You might remember that a few
months ago, Druid got close enough to graduating that the project had a
resolution approved by the dev community and the IPMC, and had been
I certainly think that would be appropriate.
I would like to submit to the board the same resolution we previously had
approved by both the dev list & the IPMC, with just the addition of some
new initial PMC members (new committers, based on previous discussion that
the initial PMC should include
Druid plans to graduate, so I hope there aren’t 3 items!
My comment on the proposed report is that it doesn’t mention the graduation
resolution. It should also say that why the resolution was previously shelved -
IP issues that have now been resolved.
Julian
> On Dec 4, 2019, at 11:25 AM,
Hi,
Currently the report will not be accpeted, under "Three most important
unfinished issues to address before graduating:" you need to list 3 items. I
can also see there is important information that has been omitted from the
report.The incubator needs this information so that it can have an
Does Druid intend to put a resolution to graduate on the agenda of the Dec 2019
board meeting?
If so that should definitely be in the report.
Julian
> On Dec 3, 2019, at 11:49 PM, Jonathan Wei wrote:
>
> Updated the section about trademarks on the wiki to the following:
>
> The PPMC has
I had problems with this as well. Check out
https://github.com/apache/incubator-druid/pull/6798 for some ways to handle
this.
On Wed, Dec 4, 2019 at 9:22 AM Krishna Likhitha Katakam <
krishna.likhi...@phonepe.com> wrote:
> Hi,
>
> I have a basic question:
> When we write a custom Druid
Hi,
I have a basic question:
When we write a custom Druid extensions module, if we have some
resources (like an HTTP client with non-daemon threads) created as part of
the module, there is no close() method currently where we can safely clean
up the resources. Could anyone help how to do this?
23 matches
Mail list logo
