Is Airflow community chart abandoned? #687
Replies: 1 comment
-
Thanks, @y-nosa for raising your concerns, I have responded below. First, this chart is not abandoned, I have simply been moving halfway around the world in the past few weeks/months (to the US, from Australia), and this has obviously taken an incredible amount of my time. I expect I will be back to somewhat normal (regarding this chart) in about 2 more weeks (today is Monday 9th January 2023). Second, regarding pending PRs, I think there is only a small number that actually affects any significant number of users (and I will prioritize getting those merged ASAP). Please reply here with any ones you are specifically concerned about and we can review them ASAP if they are actually critical. Also, In my testing, Airflow Third, regarding finding new maintainers, I am open to having others take a larger role, but to be open with you, half of the reason people use this chart is that it moves carefully (so finding another person to have actual "merge" and "release" permission would take time). Lastly, I have a few large features which have taken up most of my cycles on this chart (when I did have time over the past few months), and since the latest Airflow versions at the time were working, I did not feel the need to push a release "just because it makes the chart look less abandoned". For example, I have almost finished building a "task aware" autoscaler that selectively downscales inactive celery worker Pods in a very novel way (read more here: #339), and I hope this will become a new standard for running Airflow on Kubernetes. I am more than happy to answer other questions you might have, or review any issues/PRs which are making you worried! |
Beta Was this translation helpful? Give feedback.
-
For a long time, Airflow community chart was the best, most trusted and reliable chart out there, many thanks for outstanding work from the maintainer @thesuperzapper
Despite of we have official airflow chart now, many of us have decided to stay with the community as better structured and more dynamically evolving and easier to use.
But I clearly see a problem here, more then 8 months of pending PRs and no activity from maintainers.
Again, no other words than words of gratitude for their work, but i believe its time for maintainers to make a statement regarding their availability, make a call for other maintainers or step away and put a deprecation warning, so people can plan a transition
Beta Was this translation helpful? Give feedback.
All reactions