potiuk commented on issue #13542: URL: https://github.com/apache/airflow/issues/13542#issuecomment-907143038
@gabrielsyapse . Thanks for your comment. Maybe you do not understamd how open source and free software works, so let me explain it. Many people are working - often on their own time and with volunteered effort - so that you can use the software for free. And yeah - this means sometimes that the best way to repay it and contribute back by those users (at least a minimum effort that the users of the free software can do to thank for the effort) is to verify that what we 'think' is the fix is actually one. Surely, you can stay in 1.10 but be aware that it has reached end of life already in June and you will not get support of those (often unpaid volunteers) if you decide to stay with it. But maybe this is what you want. I am sure you can find paid support for 1.10 and expect the company doing the support makes sure that all your problems are fixed and will not ask you to verify it, it will 'just work'. Good luck with your decision. There are already a few security fixes that are only fixed in Airflow 2 that will never make it to Airflow 1.10 so you will either need someone to fix them for you or you need luck so that those are not exploited. You can learn more about it at https://youtu.be/86uqFr3LIc8 - discussion about keeping your Airflow secure that we had at the Airflow Summit. -- 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]
