potiuk commented on issue #21943:
URL: https://github.com/apache/airflow/issues/21943#issuecomment-1477661758

   > @potiuk Is there any particular reason the chart is not released yet? I 
think it'd ease on deployment. Here are the solutions that I'm considering at 
the moment:
   
   The image is released semi-regularly when release managers decide to relese 
it (I am not one for Helm Chart BTW). I think asking "reason for not releasing" 
is a wrongly asked question. It takes time and effort to publish the release. 
And it is done by volunteers when they see the time is good for it, and one 
issue affecting small group of users might not be enough to warrant it.
   
   I think the right question you could ask is "what can I do to help with 
speeding up the release". Let me answer this question instead. I think if you 
confirm that the change fixes the problem by applying the changes locally and 
confirming it here, it might definitely increase the chances that release 
managers will make a decision about releasing the helm chart.
   
   Also - as a follow up (after you confirrm it) it would immensely help if you 
help testing the release candidate. Subscribe to the devlist to get 
announcement about it and whenever we release an RC for chart, we ask people to 
test it and confirm that it works. I looked it up and I have not seen your help 
in  
   
https://github.com/apache/airflow/issues?q=is%3Aissue+%22status+of+testing+Apache+Airflow+Helm+Chart%22+
 so I think that is a great idea to get involved and help with it when we do 
release it.
   
   Can we count on your help there @elongl to verify and confirm it and then 
later take part in testing when an RC is out? That would certainly help to 
speed up the release.
   
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to