mik-laj commented on a change in pull request #8807: URL: https://github.com/apache/airflow/pull/8807#discussion_r422771071
########## File path: dev/BACKPORT_PACKAGES.md ########## @@ -0,0 +1,119 @@ +<!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +# Backport packages + +# Overview + +This document describes process of preparing backport packages for release and releasing them. +Backport packages are packages (per provider) that make possible to easily use Hooks, Operators, +Sensors, Protocols and Secrets from the 2.0 version of Airflow in the 1.10.* series. + +Once the packages are released you can simply install them with + +``` +pip install apache-airflow-backport-providers-<PROVIDER>[<EXTRA>] +``` + +Where <PROVIDER> is the provider id and <EXTRA> is optional extra packages to install. The +provider packages dependencies and extras are described in the README.md files in each provider +package (in `airflow/providers/<PROVIDER>` folder) as well as in the PyPI installation page. + +Backport providers are great way to migrate your DAGs to Airflow-2.0 compatible DAGs. You can +switch to the new Airflow-2.0 packages in your DAGs, long before you attempt to migrate +airflow to 2.0 line. + +## Deciding when to release + +Backport packages are released separately on ad-hoc basis, whenever we find that given provider needs +to be released - due to new features or due to bugfixes. Each backport package is released separately +- although we decided to release all backport packages together in one go 2020.05.10. + +We are using [CALVER](https://calver.org/) versioning scheme for the backport packages. We also have +automated way to prepare and build the packages, so it should be very easy to release the packages often and Review comment: ```suggestion an automated way to prepare and build the packages, so it should be very easy to release the packages often and ``` ---------------------------------------------------------------- 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]
