ashb commented on a change in pull request #7391: [AIRFLOW-6663] Prepare backporting packages URL: https://github.com/apache/airflow/pull/7391#discussion_r380941844
########## File path: README.md ########## @@ -107,6 +108,33 @@ unit of work and continuity.  +## Airflow Versions, backporting packages and future upgrade path + + +Currently stable versions of Apache Airflow are released in 1.10.* series. We are working on the +future, incompatible version of Airflow from the 2.0.* series. It is going to be released in +in 2020. However the exact time of release depends on many factors and is yet unknown. +We have already a lot of changes in the hooks/operators/sensors for many external systems +and they are not used because they are part of the master/2.0 release. + +In the Airflow 2.0 - following AIP-21 "change in import paths" all the non-core operators/hooks/sensors +of Apache Airflow have been moved to the "airflow.providers" package. This opened a possibility to +use the operators from Airflow 2.0 in Airflow 1.10 - with the constraint that those +packages can only be used in python3.6+ environment. + +Therefore we decided to prepare and release backport packages that can be installed +for older Airflow versions. Those backport packages are released more frequently. Users do not +have to upgrade their Airflow version to use those packages. There are a number of incompatibilities +between Airflow 2.0 and 1.10.* - documented in [UPDATING.md](UPDATING.md). With backported +providers package users can migrate their DAGs to the new providers package incrementally +and once they convert to the new operators/sensors/hooks they can seamlessly migrate their +environments to Airflow 2.0. + +More information about the status and releases of the back-ported packages are available +at https://cwiki.apache.org/confluence/display/AIRFLOW/Backported+providers+packages+for+Airflow+1.10.*+series + +You Review comment: ```suggestion ``` ---------------------------------------------------------------- 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] With regards, Apache Git Services
