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 project.

Because we must ensure (for instance):
- quality of the release
- the provenance of each contribution to the release and all other
licensing issues
- consensus about the status of the release

This is why there is always a VOTE and a formal process
https://www.apache.org/legal/release-policy.html

I understand that cutting a release for a helm chart is somehow different
for some aspects,
especially when we have to think about how to store the sources and the
binaries of what has been released.
In the ASF we release "sources" and "convenience binaries".

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".

Probably I am only missing some docs or some discussions, as said, I am new
to the processes of this community,
but I would like to understand if we are doing well and if we are doing the
required steps mandated by the ASF.

My understanding is that we need at least:
- creating a source tarball and put it somewhere
- run a VOTE thread
- announce the release to annou...@apache.org


If there is no process yet, then it is not a problem,  we can ask the ASF
about the best practices on releasing Helm Charts and create
our Pulsar way of releasing the Helm Chart.

Best regards
Enrico



Il giorno ven 10 set 2021 alle ore 10:45 r...@apache.org <
ranxiaolong...@gmail.com> ha scritto:

> 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 and replace the pulsar image
> in pulsar-helm-chart with the latest pulsar image.
>
> pulsar-helm-chart has its own Action CI check tool, which will check
> whether pulsar-helm-chart can work correctly under the current latest
> pulsar image. For example: our recently released pulsar 2.8.1:
> https://github.com/apache/pulsar-helm-chart/pull/161
>
> --
> Thanks
> Xiaolong Ran
>
>
> Enrico Olivelli <eolive...@gmail.com> 于2021年9月10日周五 下午2:32写道:
>
> > 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 procedure in this case ?
> >
> > Enrico
> >
> > Il giorno ven 10 set 2021 alle ore 02:56 Sijie Guo <
> > notificati...@github.com>
> > ha scritto:
> >
> > > pulsar-2.7.3
> > > <https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-2.7.3
> >
> > >
> > > Repository: apache/pulsar-helm-chart
> > > <https://github.com/apache/pulsar-helm-chart> · Tag: pulsar-2.7.3
> > > <https://github.com/apache/pulsar-helm-chart/tree/pulsar-2.7.3> ·
> > Commit:
> > > 5b10f48
> > > <
> >
> https://github.com/apache/pulsar-helm-chart/commit/5b10f48f5b271a15c000239042c507c33da16fe9
> > >
> > > · Released by: sijie <https://github.com/sijie>
> > >
> > > Apache Pulsar Helm chart for Kubernetes
> > > —
> > >
> > > This release has 3 assets:
> > >
> > >    - pulsar-2.7.3.tgz
> > >    - Source code (zip)
> > >    - Source code (tar.gz)
> > >
> > > Visit the release page
> > > <https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-2.7.3
> >
> > > to download them.
> > >
> > > —
> > > You are receiving this because you are watching this repository.
> > > View it on GitHub
> > > <https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-2.7.3
> >
> > > or unsubscribe
> > > <
> >
> https://github.com/apache/pulsar-helm-chart/unsubscribe_via_email/ACIHZNUCZD52LBJYTGO63PLUBFJVHANCNFSM4DZ232SQ
> > >
> > > from all notifications for this repository.
> > >
> >
>

Reply via email to