potiuk commented on issue #15990: URL: https://github.com/apache/airflow/issues/15990#issuecomment-1081675293
> @dstandish was the original issue resolved? In this case, please, provide corresponded note in the changelog. We are still using custom logging. In another case, please, open the issue again @egS27 - as mentioned above the original report is for 1.10 which is EOL for 10 months already and there is no expectation on any support there, including finding specific commits that fix the problem from the community. However our code and issues are fully open, and you can search for relevant issus fixing the problem. Using EOL version means exactly this - you are on your own and you should expect no support from the community for issues there. If you need support for - let me remind you the FREE software you have - from people who mostly support users like you in your free time, there are a number of companies that provide paid support for Airflow. You can easilly google them. If your expectation is some kind of SLA (and especially for an EOL version), then your best way to approach is to hire such a company. If you migrate to a supported version (Airlfow 2 generally is "live" and supported) and find similar issue (it won't be likely the same as Airflow 2 codebase and 1.10 codebase differ quite drastically) - feel free to open one, and there is a chance someone in their free time will help you (but again, if you expect some SLA, paying for support is a good option). I just write it so that you have the right expectations set. Feel free to search for relevant issue. We are not going to open the issue. -- 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]
