Thank you. This kind of work can be thankless so I just wanted to
explicitly say TY.
On Tue, Jul 11, 2023 at 10:48 PM Abhishek Agarwal
wrote:
> Since no one else has volunteered, I will take on the 1). It's possible
> that we don't get IP clearance and if we don't, we will just remove the
>
Since no one else has volunteered, I will take on the 1). It's possible
that we don't get IP clearance and if we don't, we will just remove the
code.
On Wed, Mar 1, 2023 at 7:14 AM Gian Merlino wrote:
> Not as far as I _know_, I mean.
>
> On 2023/03/01 01:43:43 Gian Merlino wrote:
> > Not as
Not as far as I do. I think we're stuck since nobody has volunteered to do one
of the two necessary things:
1) shepherd this code the IP clearance process, or
2) analyze its provenance enough to determine that IP clearance isn't necessary.
If anyone is willing to do one of the above it would be
Did we ever get to a conclusion here on IP clearance? Clint, it looks like
the helm charts are still in the Druid repo and being contributed to.
Thanks,
Xavier
On Tue, Sep 14, 2021 at 4:19 AM Clint Wylie wrote:
> My understanding of that thread suggests that
>
My understanding of that thread suggests that
https://incubator.apache.org/ip-clearance/ip-clearance-template.html
is the process that our PMC does before the IPMC can continue the
clearance process, meaning someone on our PMC fill out i think this
form
Hi Jihoon,
Last week I asked the AFS, and according to the replay, it seems that only our
IPMC has the authority to launch the IP Clearance process. FYI,
https://lists.apache.org/thread.html/rfbfc5951c4524c0e68223e4fbe05a7d7ee26c185ab557d6f77a4989d%40%3Cgeneral.incubator.apache.org%3E
Regards,
Hey Benedict,
Any updates on this issue? I think we are going to start the release
process for 0.22.0 soon.
On Fri, Jul 2, 2021 at 1:19 AM Benedict Jin wrote:
> Hi Xavier,
>
> I'm so happy to hear that and look forward to your changes will be
> contributed to upstream. In fact, Helm and
Hi Xavier,
I'm so happy to hear that and look forward to your changes will be contributed
to upstream. In fact, Helm and Operator are not in conflict, their relationship
is kind like RPM and Systemd. You can even convert Helm into Operator, or build
Operator based on Helm. And I agree with you
For what it's worth, we have been using a heavily modified version of this
helm chart at Confluent.
I would say it is good to get a Druid cluster up and running quickly, but
we had to make some significant changes to make it easier to operate a
Druid cluster.
It's great for initial deployment and
Hi Jihoon Son,
Cool, thanks a lot
Regards,
Benedict Jin
On 2021/06/21 17:10:13, Jihoon Son wrote:
> Thanks Benedict.
> You can find another example of the IP clearance process here:
> https://mail-archives.apache.org/mod_mbox/incubator-general/202106.mbox/browser.
>
> On Fri, May 28,
Thanks Benedict.
You can find another example of the IP clearance process here:
https://mail-archives.apache.org/mod_mbox/incubator-general/202106.mbox/browser.
On Fri, May 28, 2021 at 1:01 AM Benedict Jin wrote:
>
> Hi Jihoon Son,
>
> Yes, it has only been tested on the local cluster. Next, I
Hi Jihoon Son,
Yes, it has only been tested on the local cluster. Next, I will add the
automated test part.
Because Helm Chart usually releases a new version every time it is modified. So
Apache Superset has followed this approach. Of course, I agree with your
suggestion, we shouldn't release
Thanks for adding details.
Based on your answers, I assume it is not being tested. We should add
tests as soon as possible. Since you have some experience in this
area, can you add some?
I'm also not sure why Superset releases the helm chart separately. I
would suggest releasing it per our
Hi Jihoon Son,
Thank you very much for this list of questions. The following is my personal
understanding.
1. What is the current status of the project?
Helm has undergone a major version upgrade. Helm3 will continue to be
maintained, but Helm2 will no longer be maintained, and the Helm Chart
This code was developed outside of the ASF, so it’s possible that we need to go
through the IP clearance process [1]. Can a PMC member please figure out the
answer to that question, and answer on this list.
Has the Helm project given any indication whether they approve or disapprove of
the
Hi Senlan,
Thank you very much for your message and support. I have created a PR to do the
migration, referring to the experience of Apache Superset. FYI,
https://github.com/apache/druid/pull/11163 and
https://github.com/apache/superset/tree/master/helm/superset .
Regards,
Benedict Jin
On
Thanks @Benedict Jin,
It is a good idea to maintain the Druid Helm's Chart in the Apache repository.
Since "https://github.com/helm/charts; repo has been deprecation, we can't
maintain the chart, and the k8s user can't find druid chart package from
Thanks @Benedict Jin,
It is a good idea to maintain the Druid Helm's Chart in the Apache repository.
Since "https://github.com/helm/charts; repo has been deprecation, we can't
maintain the chart, and the k8s user can't find druid chart package from
Thanks Benedict,
It is a good idea to maintain the Druid Helm's Chart in the Apache repository.
Since "https://github.com/helm/charts; repo has been deprecation, we can't
maintain the chart, and the k8s user can't find druid chart package from
Hi all,
Should we maintain the Helm's Chart in the Apache Druid repository? Now the
development and maintenance of Helm's Chart has been stalled. It was previously
maintained by @maver1ck @AWaterColorPen and me (@asdf2014). Currently,
https://github.com/helm/charts/tree/master/incubator/druid
20 matches
Mail list logo
