[airflow] branch main updated: Update README_RELEASE_PROVIDER_PACKAGES.md (#28377)

[potiuk]

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

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


The following commit(s) were added to refs/heads/main by this push:
     new 3fa20e041c Update README_RELEASE_PROVIDER_PACKAGES.md (#28377)
3fa20e041c is described below

commit 3fa20e041c69e1252917cbbf49edbea1f2a046a2
Author: eladkal <45845474+elad...@users.noreply.github.com>
AuthorDate: Thu Dec 15 22:05:10 2022 +0200

    Update README_RELEASE_PROVIDER_PACKAGES.md (#28377)
    
    Make it a bit more friendly for the next one who release for the first time
---
 dev/README_RELEASE_PROVIDER_PACKAGES.md | 26 +++++++++++++++++++++++---
 1 file changed, 23 insertions(+), 3 deletions(-)

diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md 
b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index af09164873..57d7e0980d 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -229,10 +229,16 @@ cd ${AIRFLOW_REPO_ROOT}
 Verify that the files are available at
 [providers](https://dist.apache.org/repos/dist/dev/airflow/providers/)
 
-## Publish the Regular convenience package to PyPI
+You should see only providers that you are about to release.
+If you are seeing others there is an issue.
+You can remove the redundant provider files manually with:
 
-In case of pre-release versions you build the same packages for both PyPI and 
SVN so you can simply use
-packages generated in the previous step, and you can skip the "prepare" step 
below.
+```shell script
+svn rm file_name  // repeate that for every file
+svn commit -m "delete old providers"
+```
+
+## Publish the Regular convenience package to PyPI
 
 In order to publish release candidate to PyPI you just need to build and 
release packages.
 The packages should however contain the rcN suffix in the version file name 
but not internally in the package,
@@ -267,6 +273,15 @@ twine check ${AIRFLOW_REPO_ROOT}/dist/*
 twine upload -r pypitest ${AIRFLOW_REPO_ROOT}/dist/*
 ```
 
+If you see
+> WARNING  Error during upload. Retry with the --verbose option for more 
details.
+ERROR   HTTPError: 403 Forbidden from https://test.pypi.org/legacy/
+     The user [user_name] isn't allowed to upload to project [provider_name]
+
+It means that you don't have permission to upload providers.
+Please ask one of the Admins to grant you permissions on the packages you wish 
to release.
+
+
 * 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.
 
@@ -345,6 +360,11 @@ If you have providers as list of provider ids because you 
just released them, yo
 ./docs/start_doc_server.sh
 ```
 
+You should navigate the providers and make sure the docs render properly.
+Note: if you used ``--for-production`` then default of url paths goes to 
``latest``
+thus viewing the pages will result in 404 file not found error.
+You will need to change it manually to see the docs
+
 - Copy the documentation to the ``airflow-site`` repository
 
 **NOTE** In order to run the publish documentation you need to activate 
virtualenv where you installed