mik-laj commented on issue #15198: URL: https://github.com/apache/airflow/issues/15198#issuecomment-813778747
> Can you at least explore this before dismissing it completely? There have been drastic differences between the Airflow 2.0 and Airflow 1.10 releases, and cherry-picking changes are very problematic and time-consuming e.g. Airflow 1.10 still supports Python 2.7, so we need to add backward compatibility during cherry-picking. Besides, we haven't made any changes to operators for over a year now, because we started releasing backport providers, to make migrations to Airflow 2.0 a bit easier, but also so that project maintainers don't have to cherry-pick any operators related code. If we wanted to release a fix for this bug, we would therefore have to release it as backport providers. The code from the backport providers has already been removed so we would have to start creating a separate branch that would only contain the one fix. Based on this one branch, we had to prepare a new release of backport package, start voting, and then release this package. It probably took a few man-hours and took a week or more if we wanted to do it according to all the procedures we have in our community. This is an enormous amount of work that is at odds with what was previously agreed upon by the community. None of the project maintainers will be interested in doing this. If you need to fix this error, you can prepare the package yourself and publish it in your organization's private python repository. The branch to start from is [legacy-backport-cutoff-point](https://github.com/apache/airflow/releases/tag/legacy-backport-cutoff-point). The documentation and tools to build the backports are there. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
