Thanks Kaxil. Both ideas (having separate repos and having separate voting) sounds sensible to me. Cannot really think of significant drawbacks.
XD > On 1 Jul 2020, at 9:35 PM, Kaxil Naik <kaxiln...@gmail.com> wrote: > > Forgot to mention, having them in separate repo also helps in better > managing each individual artifacts. > > Each repo would have a separate Github Issue where we can track the issue > specific to Helm chart or Dockerfile. > > Regards, > Kaxil > > On Wed, Jul 1, 2020 at 8:30 PM Kaxil Naik <kaxiln...@gmail.com> wrote: > >> The PMC also needs to agree if we want separate VOTING for Docker Image >> and Helm chart, I think we do. >> >> Regards, >> Kaxil >> >> On Wed, Jul 1, 2020 at 8:06 PM Kaxil Naik <kaxiln...@gmail.com> wrote: >> >>> Hi all, >>> >>> What do you all think about having Dockerfile and Helm chart in the same >>> "Airflow" Repo vs separate? >>> >>> I feel having a separate repo for Airflow Dockerfile and Helm chart have >>> more benefits like easy to track changes (via Changelog), easy for new >>> contributors, separate release cadence. >>> >>> Currently, docker file and Helm Chart are inside the same repo and when >>> we release changelog for a new Airflow version, it would include all >>> changes (Airflow + Dockerfile + Helm chart) which I think is not that great. >>> >>> Also having them all inside a single repo means changes in Helm Chart and >>> Dockerfile can block Airflow release. We could use stable Helm Chart >>> version and Dockerfile version to test Airflow so that they are blockers to >>> release too. >>> >>> Happy to hear the thoughts from the community. >>> >>> Regards, >>> Kaxil >>> >>
