Re: Release Helm chart as a derived downstream software artifact

[Kaxil Naik <ka...@apache.org>]

Hi folks,

I am in the process of releasing a Helm Chart from Apache Airflow (https://github.com/apache/airflow/tree/master/chart). 

I have some questions around that as listed in https://issues.apache.org/jira/browse/LEGAL-573:

1) Is Helm Chart considered an official artifact as described in https://www.apache.org/legal/release-policy.html#artifacts? Or is it considered "convenience packages/binaries"

2) Do we need to go through a three 3 days voting period for releasing a new version of Helm Chart?

3) If Yes to (1) and (2), does it mean the Helm Chart should reside in the official download repository which is https://dist.apache.org/repos/dist/release/airflow/ for us (Airflow PMC Members). Some of the other Apache Projects (Tika, Pulsar, Superset to name a few) have uploaded to either Github or Apache's Jfrog Artifact repository. Example: Apache Tika: https://cwiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm | Apache Superset: https://apache.github.io/superset/index.yaml / https://github.com/apache/superset/releases/download/superset-helm-chart-0.1.2/superset-0.1.2.tgz

4) If Yes to (3) -- Helm strips comments in `Chart.yaml` file when creating a Helm Package: `helm package DIRECTORY` - which means Apache License at top of the file is stripped off which will fails License check during VOTING? Any suggestions?

5)  If Yes to (3) -- If we have Chart dependencies (airflow has a dependency on Postgres Chart) -- then it will bring the Helm Chart from Postgres which won't have License as Headers in their files. But when you run `helm package CHART_DIRECTORY` it bundles Chart + charts listed in dependencies, which makes it fail the LICENSE check again. Is the solution for it -- to just tar the source code and vote and that instead of tar generated by `helm package CHART_DIRECTORY` from source code?

My goal here is to get an agreement on the guideline which will help not only us at Airflow but all other ASF projects -- happy to help writing and adding (PR'ing) to ASF Release policies too.

Any comments/suggestions here or on the LEGAL issue I created will be very helpful.

Regards,
Kaxil

On 2021/04/22 21:49:08, Josh Fischer <jo...@joshfischer.io> wrote: 
> +1
> 
> Thank you for documenting this. It will be extremely helpful with putting
> release artifacts out there for  Heron.
> 
> - Josh
> 
> On Thu, Apr 22, 2021 at 4:15 PM Lewis John McGibbney <le...@apache.org>
> wrote:
> 
> > Hi general@,
> >
> > I wanted to loop around/close off this thread by stating what I did and
> > what the results were.
> > With Gav McDonald's kind assistance I was able to publish the tika-helm
> > [0] Charts to the Apache deployment of Artifactory/JFrog at [1]
> > The entire process is documented at [3] for anyone else who would like to
> > replicate it.
> > Maybe it is time to update [3] and add Artifactory/JFrog as a deployment
> > option?
> >
> > Literally now someone who wanted to consume this artifact could literally
> > do
> >
> > % helm repo add tika https://apache.jfrog.io/artifactory/tika
> > % helm install tika tika/tika --version ${release_version}
> >
> > Thanks
> > lewismc
> >
> > [0] https://github.com/apache/tika-helm
> > [1] https://apache.jfrog.io/
> > [2]
> > https://cwiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm
> > [3]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines
> >
> > On 2021/04/17 02:54:30, Lewis John McGibbney <le...@apache.org> wrote:
> > > Hi general@,
> > > I'm interested in releasing tika-helm [0]. tika-helm is a derived,
> > downstream Helm chart which provides a lightweight way to configure and run
> > the official apache/tika Docker image on Kubernetes.
> > > I would like the first release of this package to be an official Apache
> > release. I am therefore of the mindset that it should be treated as any
> > other official Apache source code release.
> > > Can someone point me to a precedent or policy pertaining to the
> > publication of derived downstream software artifacts such as containers,
> > Helm charts, etc.
> > > Thank you
> > > lewismc
> > >
> > > [0] https://github.com/apache/tika-helm
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> > --
> Sent from A Mobile Device
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org