Re: Release Helm chart as a derived downstream software artifact
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 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
> 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 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-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sent from A Mobile Device
>
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Helm chart as a derived downstream software artifact
+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
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 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-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Sent from A Mobile Device
Re: Release Helm chart as a derived downstream software artifact
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 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-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Helm chart as a derived downstream software artifact
Hi Zhenxu, On 2021/04/17 03:54:44, "kezhenxu94@apache" wrote: > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines The published version of that wiki page (https://incubator.apache.org/guides/distribution.html) is exactly what I am looking for. Thank you for pointing me to it. Even though a few Apache projects have already published convenience binaries to ArtifactHUB, I opened https://issues.apache.org/jira/browse/INFRA-21737 to see if INFRA would be interested in creating an Apache Org in ArtifactHUB... the same as they've done for several other platforms. Thanks everyone this has been REALLY helpful. lewismc - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Helm chart as a derived downstream software artifact
HI, Also these may help [1][2] - note one is not closed yet. Justin 1. https://issues.apache.org/jira/browse/LEGAL-270 2. https://issues.apache.org/jira/browse/LEGAL-437 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Helm chart as a derived downstream software artifact
Hi, > You may be interested in the distribution guide [1] (for incubating projects > though) > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines > I was going to suggest that as well. The guidelines under [1] should help to inform what to do, that’s not to say you can’t come up with something else. Thanks, Justin 1. https://incubator.apache.org/guides/distribution.html#release_platforms - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Helm chart as a derived downstream software artifact
Hi > 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. Right, it should follow the Apache release policy and release source tar to be an official Apache release. So there is no exception IMO to release the Helm Chart source tar. While at the same time, Apache also allows (not requires) binary releases or distributions to third-party platforms, such as Pypi, Docker Hub, npmjs.com, etc. You may be interested in the distribution guide [1] (for incubating projects though) [1] https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines > Can someone point me to a precedent or policy pertaining to the publication > of derived downstream software artifacts such as containers, Helm charts, etc. There are also some TLPs [2] that did Helm Chart releases just for your reference. [2] https://artifacthub.io/packages/helm/apache-solr/solr-operator (https://github.com/apache/solr-operator) https://artifacthub.io/packages/helm/apache/pulsar (https://github.com/apache/pulsar-helm-chart) https://github.com/apache/skywalking-kubernetes > Thank you > lewismc > > [0] https://github.com/apache/tika-helm > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > — Zhenxu Ke (柯振旭) GitHub @kezhenxu94 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Helm chart as a derived downstream software artifact
Hi, hope these documents can help you. Release Management: http://incubator.apache.org/guides/releasemanagement.html Assembling LICENSE and NOTICE files: https://infra.apache.org/licensing-howto.html ASF 3RD PARTY LICENSE POLICY: https://apache.org/legal/resolved.html Lewis John McGibbney 于2021年4月17日周六 上午11:10写道： > I found the following... > > https://lists.apache.org/thread.html/b40f5e388f14948722c150933106063fa73dc297149e7e63d3322458%40%3Cgeneral.incubator.apache.org%3E > But I'm still not clear on what is allowed and what is not...! > Can someone please clarify? > Thanks > > On 2021/04/17 02:54:30, Lewis John McGibbney 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-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best wishes！ CalvinKirs
Re: Release Helm chart as a derived downstream software artifact
I found the following... https://lists.apache.org/thread.html/b40f5e388f14948722c150933106063fa73dc297149e7e63d3322458%40%3Cgeneral.incubator.apache.org%3E But I'm still not clear on what is allowed and what is not...! Can someone please clarify? Thanks On 2021/04/17 02:54:30, Lewis John McGibbney 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-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
