Il giorno ven 10 set 2021 alle ore 11:38 r...@apache.org <
ranxiaolong...@gmail.com> ha scritto:
> > Creating a tag on the git repo is not enough to say that we cut a
> release,
> > but for how this stuff works it makes the chart
> > usable from users and we must take this into consideration as an
> Creating a tag on the git repo is not enough to say that we cut a release,
> but for how this stuff works it makes the chart
> usable from users and we must take this into consideration as an "official
> release".
Yes, I fully recognize that in pulsar-go-client, creating a tag can already
meet o
Xiaolong,
Thanks for your information, very useful.
I believe that we could make this better (and probably we "must").
Cutting a "release" in the ASF is a more involved and formal process.
Releasing a project must run through a formal validation process, and must
be validated by the PMC of the pr
Hello Enrico:
The current release of pulsar-helm-chart does not have a related process to
illustrate this.
In a conventional way, each release owner will push the related docker
image to the docker hub after each release is completed. At this time, we
will go to pulsar-helm-chart to open a new pr
Hello,
I apologise in advance, but I am still new to some of the procedures here.
I just noticed a new release of the Pulsar Helm Chart.
How does the release of the Helm chart work ?
Apparently this is something that is not released using the usual process.
Can anyone post some link to the proced
