potiuk commented on PR #49747:
URL: https://github.com/apache/airflow/pull/49747#issuecomment-2875788408

   > This journey from Airflow 2 to 3 has made me reluctant to be the first to 
"eat the crab" again. And I hate being proven right once more… after building 
and installing the latest Celery provider from main, I'm still getting 
bombarded with ConnectError: [Errno 111] Connection refused if I don't set the 
AIRFLOW__CORE__EXECUTION_API_SERVER_URL environment variable somewhere.
   
   However, we greatly appreciate your efforts @zachliu -> yes, there are 
teething issues, and being an open-source project, it's almost a given that the 
first brave users who will start testing and using Airflow 3 will find things 
that we have not thoguht about and that's the only way we can actually get to 
know about those issues and fix them. There is no software with bugs, and no 
amount of "lab" tesitng is able to find all those - especially if you give your 
software for free and there is noone who will pay for that extra testing. So 
effectively this is the price you pay for using sotware that cost you `0 USD`. 
And we consider it a great contribution from people like you who are brave 
enough and supportive enough and understand that there might be issues - what 
we offer instead is a close cooperation, trying to find mitigations and offer 
ways to try and tests main versions and RC candidates as soon as we have them. 
   
   I think - to be honest - it was great getting your initial feedback and 
issue reports and we will continue to diagnose and fix issues as they come. I 
think the power of Airlfow come from the power of the community that is both 
helpful and understands that there are some initial teething pains - and goes 
through those pains together with us.
   


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to