potiuk commented on issue #52368: URL: https://github.com/apache/airflow/issues/52368#issuecomment-3274975392
> [@potiuk](https://github.com/potiuk) sure, that's clear. I'm just wondering how's possible so many "basic" features went broken during 3.0 transition without notice. I have already quite extensive list of things to fix. I hope I'll be able to provide patches before 3.1 lands, but it seems it is in beta now. 🙏 Adding this to my list. Some things are "basic" for some people, and some are not. Manye of our users are successfully using Airlfow 3 already and they are happy, yes, there were some feture parity issues and some bugs that the whole community now works on fixing after almost complete rewriting of parts of the code. And you have to remember that you get that software for 0 USD, with no guarantees and there are 100s of volunteers working days and nights so that you can do it, and as a Apache Software Foundation project - which is volunteer led, and community developed, contributing back by providing fixes or - the very least - testing some changes is the least you can do to contribute back. Remember once again - you paid exactly 0 USD or any other currency for the software. Giving back by helping to solve issues in the redesign seems like small price to pay for software that saves you and your company a lot of time an money. -- 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]
