[airflow] branch master updated: Update the docs to release Providers (#14842)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/master by this push:
     new 34008b5  Update the docs to release Providers (#14842)
34008b5 is described below

commit 34008b593cb32ca6696bdc0e5609059bb25736ed
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Thu Mar 18 01:15:53 2021 +0000

    Update the docs to release Providers (#14842)
    
    While releasing the ES Provider 1.0.3, I updated the docs
    to release providers.
    
    One section was duplicate and there was other minor fixes
---
 dev/README_RELEASE_PROVIDER_PACKAGES.md | 62 +++++----------------------------
 1 file changed, 9 insertions(+), 53 deletions(-)

diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index 3842bc3..0584a01 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -36,6 +36,7 @@
   - [Verify by Contributors](#verify-by-contributors)
 - [Publish release](#publish-release)
   - [Summarize the voting for the Apache Airflow release](#summarize-the-voting-for-the-apache-airflow-release)
+  - [Publish release to SVN](#publish-release-to-svn)
   - [Publish the Regular convenience package to PyPI](#publish-the-regular-convenience-package-to-pypi-1)
   - [Publish documentation prepared before](#publish-documentation-prepared-before)
   - [Add tags in git](#add-tags-in-git-1)
@@ -255,7 +256,7 @@ export AIRFLOW_SITE_DIRECTORY="$(pwd)"
 ```shell script
 cd "${AIRFLOW_REPO_ROOT}"
 ./breeze build-docs -- \
-  --for-production
+  --for-production \
   --package-filter apache-airflow-providers \
   --package-filter 'apache-airflow-providers-*'
 ```
@@ -642,7 +643,7 @@ Cheers,
 
 
 
-### Publish release to SVN
+## Publish release to SVN
 
 The best way of doing this is to svn cp  between the two repos (this avoids having to upload the binaries
 again, and gives a clearer history in the svn commit logs.
@@ -699,61 +700,16 @@ svn commit -m "Release Airflow Providers on $(date)"
 ```
 
 Verify that the packages appear in
-[backport-providers](https://dist.apache.org/repos/dist/release/airflow/providers)
-
-### Publish the final version convenience package to PyPI
-
-Checkout the RC Version for the RC Version released (there is a batch of providers - one of them is enough):
-
-```shell script
-git checkout providers-<PROVIDER_NAME>/<VERSION_RC>
-```
-
-In order to publish to PyPI you just need to build and release packages.
-
-* Generate the packages.
-
-```shell script
-./breeze --backports prepare-provider-packages both
-```
-
-if you ony build few packages, run:
-
-```shell script
-./breeze prepare-provider-packages <PACKAGE> ...
-```
-
-In case you decided to remove some of the packages. remove them from dist folder now:
-
-```shell script
-ls dist/*<provider>*
-rm dist/*<provider>*
-```
+[providers](https://dist.apache.org/repos/dist/release/airflow/providers)
 
 
-* Verify the artifacts that would be uploaded:
-
-```shell script
-twine check dist/*
-```
-
-* Upload the package to PyPi's test environment:
-
-```shell script
-twine upload -r pypitest dist/*
-```
-
-* Verify that the test packages look good by downloading it and installing them into a virtual environment.
-  Twine prints the package links as output - separately for each package.
-
-* Upload the package to PyPi's production environment:
-
-```shell script
-twine upload -r pypi dist/*
-```
+## Publish the Regular convenience package to PyPI
 
+* Checkout the RC Version for the RC Version released (there is a batch of providers - one of them is enough):
 
-## Publish the Regular convenience package to PyPI
+    ```shell script
+    git checkout providers-<PROVIDER_NAME>/<VERSION_RC>
+    ```
 
 * Generate the packages with final version. Note that
   this will clean up dist folder before generating the packages, so you will only have the right packages there.