kaxil edited a comment on issue #8582: URL: https://github.com/apache/airflow/issues/8582#issuecomment-620004504
**Notes from our discussion**: - Our Release Guide: https://cwiki.apache.org/confluence/display/AIRFLOW/Releasing+Airflow - This has details (or links to other docs) on how to create your GPG KEYS and upload them to https://dist.apache.org/repos/dist/release/airflow/KEYS. And has the details of the actual release process. Feel free to create a separate section (or a Subpage) for releasing the Backport package. - Our normal RC Voting rules apply - Versioning: CALVER (YYYY-MM-DD) - Release backport packages for all the providers for the first one. After that they can be released individually - Docs: The Readme inside each Provider backport package will contain details about the list of new Operators/Hooks/Secrets etc - ReadtheDocs: Create a new page that shows all the Backport Packages that were released with Changelogs (We should not add this page on airflow.apache.org doc site, so maybe add a RTD env var to ignore - ???) - Have 'backport' in the name (e.g `apache-airflow-backport-provider-google`) of the final release candidate and the package to future-proof us if we ever separate the provides folder to separate repos - Create separate folder for each provider `downloads.apache.org/airflow/backport-providers/$provider/$ver/$x.whl` - To get files in to downloads.apache.org we do it via SVN, and we should obviously upload it to dev/ first (which is what your release guide says to do) - We will have a single Git Tag for each Backport Release (e.g backport-provider-2020-04-27) can have multiple providers released under it but a Single Git Tag ---------------------------------------------------------------- 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]
