thesuperzapper commented on issue #10523: URL: https://github.com/apache/airflow/issues/10523#issuecomment-687113195
@potiuk, can you confirm if you plan to have the official helm chart releases tagged to airflow releases? If so, I personally think that will cause big issues, as the helm chart and airflow itself are significantly different artifacts from a user perspective. (As an example, the helm chart that may not even need to change between airflow releases) Almost every other project I am aware of has their helm chart releases completely independent of the app itself, and stored in a seperate repo. (Otherwise it would be impossible to push a critical fix for some helm specific issue without an app release) Therefore, I think the [discussion about apache/charts](https://lists.apache.org/thread.html/rcb608739206d788785081073a0deb417ffa9981634975fc5525dc769%40%3Cdev.community.apache.org%3E) is important, because I expect we will have to move the offical chart out of this repo before we can properly release it. If we did move to an `apache/charts` style repo, then we could easily have both the old `stable/airflow` and the new one in from this repo until they reach feature parity, after which we would drop support for `stable/airflow`, and help users with a migration guide. (This is important, because `stable/airflow` will have to go somewhere before the November deadline, as it is widely used, and there is not currently an alternative) ---------------------------------------------------------------- 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]
