potiuk commented on pull request #8777: URL: https://github.com/apache/airflow/pull/8777#issuecomment-638120442
> > Great. Then we will have to aadapt our plans and make whatever everyone will be doing if "official" helm chart will no longer be official. > > Regardless of that the Dockerfile an Helm Chart will be here to stay and once we stabilise it and make both image and helm robust we will find a good place for both I am sure. > > In terms of our workflow Jarek how about this as a work flow: > > We have this repo be the source of truth/latest version (which makes the Airflow CI much easier) and then we "publish" releases as static files like a normal release artifact to https://downloads.apache.org/airflow/helm-chart/ (just an example. It could live on airflow.apache.org, but I think ASF would prefer us to have the blob live on downloads.a.o) Absolutely! I think we are in perfect sync with the "target" approach. We even have a point about it in the AIP-26 ("Release process is updated to release the images as well as pip packages"). Helm Chart was added later but I think it applies to all - images, Dockerfiles, HelmCharts, and possibly even production-ready docker-compose.yml which we are also going to have (#8605) - we should definitely have such officially released set of artifacts. We can do it in various ways. One of them will be separate repo (which in the absence of official repo where we can publish it - should be our own), Or we could use release artifacts, or even packages feature of github. I think we should decide once we implement most of the outstanding issues and have the CI + Helm Chart working well and tested in our CI test process. I am ok with either solution agreed between the committers there as long as we keep the development version in Airflow repo and make them part of the CI process. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
